Roland, You may want to read upon Stepen E. Bacher's response(at the bottom) in this topic
https://groups.google.com/forum/#!msg/bit.listserv.tsorexx/4TKYMruiMU4/iVJ-MaRHVdYJ Kolusu IBM Mainframe Discussion List <[email protected]> wrote on 09/11/2015 12:09:32 PM: > From: Roland Kinsman <[email protected]> > To: [email protected] > Date: 09/11/2015 12:09 PM > Subject: Re: REXX Exec Abend S106 > Sent by: IBM Mainframe Discussion List <[email protected]> > > Thanks for quick replies. > > I'll look into using ATTACHMVS instead of CALL, or find a way to add > logoff into the loop. That one looks very promising if I can pull it off. > > I'm calling both programs using TSOEXEC CALL *(xxx). > > We're already using REGION=0M. > > Not sure what language the programs are in--they are both utilities > from different vendors. The first utility is doing the open/close > of the members. > > I'm getting the member names using LMMLIST. > > I am using DELSTACK in my loop, as I use a number of QUEUE > statements. Not sure if this has the same effect as DROP. > > I'm not actually processing the contents of the members. The first > program in the loop processes the PDS member, then the second > program processes the output of the first one. For the first > program in the loop, one of the parms is the name of the PDS, and > the member name is on one of the control cards. My REXX generates > the control cards then calls the first program. Based on the > messages from the job, it appears that the storage problem is in the > second program. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
