In converting from another product to CA Deliver, the client created new report definitions.
In running the corresponding application jobs against these new definitions, the client found that some of the reports are being intercepted and others were not.
They use RMOPARM OUTPUT=YES.
Why are reports still going to the other product, which need to be shut down?
Why do some reports seem to be dropped from the Deliver capture when they appear to match the SYSOUT definitions defined?
Release : 12.2
Component : CA Deliver
The client had the following in their JCL:
//MCROUT OUTPUT JESDS=ALL,DEFAULT=YES,DEST=LOCAL,CLASS=*
//RMDS01 OUTPUT CLASS=R,WRITER=RMDS,FORMS=M630,DEST=A40JES
//RMDS02 OUTPUT CLASS=R,WRITER=RMDS,FORMS=M631,DEST=A40JES
//XXXXXXXX DD SYSOUT=(,),OUTPUT=(*.MCROUT,*.RMDS01)
The following is from the Deliver Reference Guide:
If a SYSOUT DD statement references more than one //OUTPUT statement, Deliver uses only the first statement to obtain print attributes.
Other statements are ignored.
Given the above, the attributes CLASS=R, WRITER=RMDS, FORMS=M630 (and M631), and DEST=A40JES are being ignored.
That is the reason why the reports are not being processed as expected.
The ways to address the situation are:
. Change the Deliver definitions, to not use F=..., but to use the Stepname and DD from the JCL.
. Alter the application job JCL, so that the entry uses the FORM name itself (SYSOUT=(x,,form)), rather than a referback.