is CA/VIEW taking the place of the JES output queue?
I am unaware of how to use REXX to read the queue (and I have not worked with CA/VIEW).
My first thought would be to copy the output (lets call it SYSOUT) from the queue to a flat file (which can be done in JES) and then just process thru the JCL looking for DD cards.
for info on REXX for z/OS : http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/SEARCH?SEARCHREQUEST=REXX&Book=IKJ4A370&DN=SA22-7790-07&DT=20060626210253&TYPE=FUZZY&RANK=RANK&SEARCHTOPIC=TOPIC&SEARCHTEXT=TEXT&SEARCHINDEX=INDEX&RESULTS=WINDOW&PATH=/bookmgr_OS390/libraryserver/zosv1r10/&CASE=zosv1ra0.bkc&SHELF=EZ2ZBK0G.bks
Karl here. Maybe I can help out.
At one time, I was trying to interface with SAR from within a REXX. I never got it working, because I think there was some setup required in the installation of CA/VIEW that didn't get done at my site.
Here is the exec that I was working with, keeping in mind that I never got it working. I'm pretty sure I found an example to go on in CA's Installation libs somewhere.
/* REXX */
SAMPLE XPVIEW/ISERVE GREXX EXEC
THIS EXEC WILL LOOK AT THE USERS IN THE UNICENTER CA-VIEW
DATABASE AND CHANGE THE BANNER TO PRODBAN FOR THOSE USERS
WHOSE BANNER IS CURRENTLY SET TO TESTBAN.
ADDRESS XPVIEW /*SET THE HOST COMMAND ENV */
XPVIEW.DBASE = 'XXX.VIEWDB03' /*SET THE XPVIEW DATABASE */
'LIST GEN=* ID=MYJOB096'
After failing at that approach, I switched to a Batch job, with one step to read the output from SAR, and a second step to read in and parse out the results.
//STEP01 EXEC PGM=SARBCH
//SYSPRINT DD SYSOUT=*
//REPORT DD SYSOUT=*
//SARPRINT DD DSN=USER.SAR.LISTING,
//SYSIN DD *
/PRINT ID=MYJOB096 DDNAME=SARPRINT
//STEP02 EXEC PGM=IKJEFT01,DYNAMNBR=30,REGION=0M
//SYSEXEC DD DSN=USER.ISPF.EXEC,DISP=SHR
//SYSTSPRT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//TRACKING DD SYSOUT=*
//UPDATES DD SYSOUT=*
//SARIN DD DSN=USER.SAR.LISTING,DISP=SHR
//SYSTSIN DD *