But, if you do like Alan suggests, you can not erase the text following the command you write in an RDRLIST line: because: if yu wipe out the spoolid, RDRLIST's command processor (EXECUTE XEDIT) no longer knows which spool file to handle.
To know a spoolid of a specific file (or a few): write "M *" in front of the file, and you'll get the spoolid in a message; to view the spool id and the name and type, enter "M * / /nt" (M is the abbreviation of MESSAGE/MSG) 2010/1/18 Alan Altmark <[email protected]> > On Monday, 01/18/2010 at 03:26 EST, Edward M Martin <[email protected]> > wrote: > > Thanks. I can work with this. Other than looking in the RDRLIST SEXEC > > Y, is there a layout of all that the RDRLIST has available? > > No, there is no published layout of what each line has in it. If you have > a 90-column display, you can > 1. DEFAULTS SET RDRLIST PROFILE USERRLST > 2. Create USERRLST XEDIT A > /* */ > arg parms > "COMMAND MACRO PROFRLST" parms /* Invoke the REAL profile */ > if rc <> 0 then exit rc > 'COMMAND SET WRAP ON' /* Because I like it */ > queue 'COMMAND VERIFY 1 79 104 108' /* Show me the spool id */ > > The 'queue' is needed because PROFRLST puts things in the stack, and those > are executed only after you exit from the profile. Extra points are > awarded to the student for successfully programmatically extracting the > header line and updating it to include "Spid" for the last column. > > Alan Altmark > z/VM Development > IBM Endicott > -- Kris Buelens, IBM Belgium, VM customer support
