book
Article ID: 186198
calendar_today
Updated On:
Issue/Introduction
In moving some View SARSTC sysouts to a View database, they went to a dataset instead.
Is there a way, to collect the dataset to a View database?
Also, there are sysouts in a started task, that get split in terms of DDs in CA view.
How can these separate DDs be moved to a single entry?
Resolution
To send a dataset to be collected by CA View, JCL similar to the following can be used:
//XXXXXXXX JOB ...
//GENER EXEC PGM=IEBGENER
//OUTPUT1 OUTPUT DEST=dest,FORMS=form
//SYSPRINT DD SYSOUT=X
//SYSUT1 DD DISP=SHR,DSN=your_DSN <=== Modify
//SYSUT2 DD SYSOUT=x,OUTPUT=*.OUTPUT1
//
The idea with the above is that there is the use of CLSL/DEST/FORM, which would be used tollect to View.
Note: The name of the sysout in the database would be from the jobname used in the job.
The reason why there are separate reports from the same task or function, which were collected at the same time, is because the reports have different attributes.
Class, Destination, and Form are only a few of the hundreds of attributes that are used that can differentiate reports.
In the client's output listing, there were some sysouts with only "SYSOUT=*", while some sysouts had "SYSOUT=*,FREE=CLOSE".
The sysouts with FREE=CLOSE are released when the task is brought down.