Subject: RE: z/OS PL/I Program Abending
From: Chuck Arney (carney@illustro.com)
Date: Fri Aug 21 2009 - 11:50:22 EDT
Bob, what does your z/OS JCL look like? If it is a DD * file, it should remain 80 byte records. Chuck Arney illustro Systems International, LLC http://www.illustro.com Internet-enable your applications with z/Ware V2 Voice: 214-800-8900 X#5562 -- This e-mail is private and may be confidential and is for the intended recipient only. If misdirected, please notify us by telephone and confirm that it has been deleted from your system and any copies destroyed. If you are not the intended recipient you are strictly prohibited from using, printing, copying, distributing or disseminating this e-mail or any information contained in it. We use reasonable measures to virus scan all E-mails leaving illustro but no warranty is given that this E-mail and any attachments are virus free. You should ensure you have adequate measures in place for your own virus checking. > -----Original Message----- > From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf Of > rbotsis@aol.com > Sent: Friday, August 21, 2009 10:41 AM > To: VSE Discussion List > Subject: z/OS PL/I Program Abending > > All, > > > I'm gonna try and make this as brief as possible as I don't want to > make it too long for fear that someone, who may know the answer/s, > won't read it if it's too long. > > I am submiting JCL (a job) to z/OS using PWRSPL. Inside this job a PL/I > program I wrote executes to submit JCL (another job) back to z/VSE > using INTRDR. The statements being sent back to z/VSE are masked with a > dash in the 1st byte and the PL/I program shifts the record to the > left, thus removing the dash. The PL/I program is blowing up due to a > UNDEFINEDFILE condition. The condition is being raised because it > appears that even though the records being submitted to z/OS are 80 > bytes via PWRSP (I put them in the RDR que and looked at EACH record > length using IPW$$DD), JES is somewhere/somhow changing them to some > other recordsize or blocksize. The problem is that I don't know what > the size they are being changed to. If someone can answer at least ONE > of the following questions it may help me to resolve this situation: > > 1). When PWRSPL is used, with XDEST=CDC on the * $$ JOB statement (CDC > is the NODE name for this particular z/OS system) what recordsize > and/or blocksize does JES change it to. > > 2). If no one knows the above, what statement/s can I put in the PL/I > program to ignore the condition which would allow the program to > continue and still process the records. > > 3). If no one knows the above, where in the PL/I dump, which is > produced on z/OS, can I determine the REAL recordsize and blocksize, > assuming PL/I provides this? > > 4). Failing any of the above, what else can I do to resolve this problem?
This archive was generated by hypermail 2b25 : Wed Sep 02 2009 - 20:20:10 EDT