Is this homegrown or vendor product like Mobius, VPS or other like product?
There is no obvious reason, short of reading a dump, to know what one job works and one job does not. If vendor product, then I would contact the vendor. Otherwise I would contact IBM - probably JES2 Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Robin Atwood > Sent: Thursday, January 05, 2017 7:14 AM > To: [email protected] > Subject: Re: IEC141I 013-A8: how to read VS data sets? > > The JCL is not relevant, both applications are servers that use dynamic > allocation. They are using SAPI to read the JES spool. The message is > > IEC141I 013-A8,IGG0199G,TAURISP3,TAURISP3,SYS00002 > > The spool data set is allocated to SYS00002. I am really interested in advice > about reading VS data sets, what access method to use, etc. > > Thanks > Robin > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Lizette Koehler > Sent: 05 January 2017 19:47 > To: [email protected] > Subject: Re: IEC141I 013-A8: how to read VS data sets? > > Robin, > Please delete any part of the email you did a REPLY to that does not pertain > to your question. It tends to confuse the issue. > > Next, I am not clear on Reading a VS on JES2 Spool. JES2 Spool has its own > unique process for creating SYSOUT. So if you could explain further that > could help. > > If you are asking about a job that abended when trying to Read a VS dataset > and got an S013-A8, then that is a different question. > > When I look up your abend code > > An incorrect record format was requested for a SYSIN, SYSOUT, or subsystem > data set with BSAM or QSAM or for a z/OS UNIX directory with BPAM. One of the > following conditions was detected: > > RECFM=D was specified. > Variable spanned records (VS or VBS) were requested for input. > Both ANSI and machine control characters were specified. > > Please show the JCL from the job that runs good and the job that fails. You > can change the dataset name and I think we only need the JCL to see the way it > is coded. > > Again, you would read SYSOUT On JES2 not a VS dataset on JES2. Unless your > application is trying to run a JES2 SSI function to read SYSOUT. > > Please provide further details. > > And if you could post the complete IEC141 I message, that would also be > helpful. Again just change the dataset name. > > Lizette > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] > > On Behalf Of Robin Atwood > > Sent: Thursday, January 05, 2017 5:31 AM > > To: [email protected] > > Subject: IEC141I 013-A8: how to read VS data sets? > > > > One of our apps abends if trying to read a VS data set on the JES2 > > spool. The message manual tells me this is because it is not allowed > > to read VS SYSOUT using QSAM. Yet we have another application which does > exactly that. > > Furthermore, after one day of staring at the code I cannot see any > > functional difference between the two routines: > > both use identical DCB/DCBEs. SDSF can read the data set of course, > > but I expect it has some internal interface. So I searched on what is > > the correct way to read VS data sets and found virtually nothing. > > Anybody got any experience of this? > > > > Thanks > > Robin ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
