OPSLOG EXPORT in JSON Format - batch job sample
Article ID: 381847
Updated On: 01-08-2025
Products
Issue/Introduction
When PTF LU12196 is applied, the OPSVIEW Option 7.1.7 is added and it is possible to export the OPSLOG in JSON format .
Choosing the batch mode to do the RESTORE, the jcl built by OPS looks as follows:
//EXPORT EXEC PGM=OPRESTLG,PARMDD=PARMDD
//OPS$OPSS DD DUMMY
//STEPLIB DD DISP=SHR,DSN='ops140.CCLXLOAD'
//EXPORTDD DD DISP=SHR,DSN=export_output_dsname
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//PARMDD DD *
BEXPORT ARCHIVE GLOBAL0.EXPORT.OPSDATA.00FC4700.T0162302.0
/*
In the JCL text, the real DSNAME of the OPSLOG dataset to be exported is not included, but only the name of a Global Variable built by OPS when the jcl is created (in red in the above jcl).
The request is to have a sample jcl that points to the real OPSLOG dsname to be exported.
Resolution
OPRESTLG can EXPORT an archive OPSLOG dataset, using the following JCL:
//EXPORT EXEC PGM=OPRESTLG,
// PARM='EXPORT OTEL ARCHIVE LLLLLLL.ARCH.XXXX.G0031V00'
//OPS$OPSG DD DUMMY
//STEPLIB DD DISP=SHR,DSN=...OPS140.CCLXLOAD
//EXPORTDD DD DSN=LLLLLLL.EXPORT.TEST,DISP=SHR
The entire archive is exported, with filtering.
The fully qualified DSN must be specified in the PARM field, or in a PARMDD reference, as using GDG reference (0) or (+1) would not work .
OPS$OPSG DD DUMMY refers to the subsystem name OPSG
'OPSG' should be replaced by the OPS subsystem name defined during the installation. If the default value for the 'SUSSYSNAME' OPSPARM is used, then this DD statement could be removed.
This job comes from the skeleton found in CCLXSENU(OP71XJOB)
Feedback
