Create unique Sysout Id entries in OM View
search cancel

Create unique Sysout Id entries in OM View

book

Article ID: 23908

calendar_today

Updated On:

Products

Deliver View Output Management Web Viewer

Issue/Introduction

I have the same STC names running on multiple LPAR's each writing to the same VIEW database. In VIEW how do I distinguish what LPAR the Output originated from ? 

Take TCPIP for example.

TCPIP runs on all LPAR's with the same name and during shutdowns the SYSOUT is archived to View. During some weekends, all LPAR's are shutdown and each LPAR produces a copy of TCPIP which goes to View and each log has the same name. This makes JOBLOG research very cumbersome, since all the TCPIP outputs must be reviewed for the date until the log for the correct LPAR is found.

Is there any easy way to differentiate the output from LPAR XXX1 and LPAR XXX2?

Environment

  • View®
  • Deliver™
  • Output Management Web Viewer™
  • OM View for z
  • Output Management View® for z/OS
  • Output Management Deliver™ for z/OS

Resolution

You can use the External Writer field in your JCL with the $ command to help here.

Example:

The JCL statement is as follows:

//SYSUT2 DD SYSOUT=(V,$LPAR3)

Class V is picked up by View - the text that follows the $ in the writer field is appended to the report - when you run the same job through your View system changing the writer each time

from LPAR1 to LPAR2 to LPAR3 - this is what you will see in your View database:

CA-View ALL --------------- Sysout Selection List ----------- 
Command ===>                                                 
 
   Sel  Sysout ID                        Arch Date    Time   Loc  
==> TCPA* * * * TCPAJOBLPAR1 02/24/2010 04:05 DISK TCPAJOBLPAR2 02/24/2010 04:06 DISK TCPAJOBLPAR3 02/24/2010 04:06 DISK

Now you can easily identify what task the output comes from.