Dear Scott, Thanks very much for thoughtful e-mail suggesting I could impersonate "senior systems programmer". Am already putting together fake resume that shows I have received graduate degree from Cal Tech in quantum-bonnano-nano-computing. Also, my favorite color is blue and my favorite flavor is "Pez"! Hope one of the other Linux guys can take advantage of opportunity in case I don't get the call. Enjoyed very much cookout over at your place. Am now completely hooked on brownies. Also, impressed with intra-state driveway system in your back/side yard. Keep it up! Is Linux group going to meet tomorrow, 7:00 Thursday, at Westport library? Yes? Will try to be there. Pretty busy right now, but I will try. Please respond. Your pal, Tom On Thu, 08 Jul 2004 02:38:11 +0000 Scott Harris <sharris64109@xxxxxxxxxxxxx> writes: > I know a headhunter who's looking for a senior systems programmer and > > needs a list of candidates by the end of the week. I don't qualify > myself but in case any of you guys do, here's the spec: > > Position details: > 1) 2 month contract to hire position > 2) Kansas City, Mo is location > 3) Salary - OPEN ($40 to $45 per hour to start, conversion $85K + > depending on strength) > 4) Start Date - ASAP > 5) Background and fingerprint check required > > JOB DESCRIPTION: SENIOR SYSTEMS PROGRAMMER > > Established company looking for experienced audit engineer > with broad exposure in the following specific Mainframe Operating > Systems > and Software: z/OS 1.3 with various LPARS UNIX System Services, V/M > Linux, > WebSphere Application Server, Tivoli Storage Manager, DB2, CICS, > Oracle, > SAS > products, Lotus Domino, and COTS. > We desire the candidate to have hands-on mainframe experience and > have an > understanding of the following: > * The CSVRTLxx, IEASYSxx, IEFSSNxx, and SMFPRMxx PARMLIB members > must be > reviewed for the security impacts for OS/390 UNIX. > * The OMVS must be defined as a subsystem in the system parmlib > (IEFSSNXX). > * A started task id entry must be created for each queue manager > started > task procedure and distributed queuing started task procedure. > * Process security must be active, and all profiles ssid.processname > > must be > defined in the MQPROC class. > * Access to the JES2 commands must be restricted a minimum number of > authorized personnel, and all access logged on the system. > > -- Scott > > > >