Move Reports Between OM View Databases

Products

• OM View

Issue/Introduction

This document describes procedure a procedure that you can use to move reports between two View databases.

Environment

Output Management View® for z/OS, OM View

Resolution

This procedure may be used to move reports from one View database to another View database.

Prerequisites:

• This procedure can be used to move TEXT reports only. (Not AFP or XEROX).
• The target View and the receiving View would need to share a JES queue.
• All reports from the target database that need to be moved had to have been collected by the View started task (SARSTC), not sent to View by way of Deliver Direct Archive.
• This can be verified by confirming a value of SAR is reflected in the ORIG column on the Sysout Selection List screen.
• Any logical views, to be used, must be in place.
• The SARINIT ARCHCNG= parameter should be set to ARCHCNG=NO

Process:

• Run SARBCH /LOAD on each individual report to be moved, putting the report into it's own sequential dataset:

  //SARBCHPR JOB ...
  //STEP1     EXEC PGM=SARBCH,PARM='VIEW.DB1'          <=== Modify DB name
  //*STEPLIB   DD DISP=SHR,DSN=VIEW.CVDELOAD          <=== Modify, if needed
  //SYSPRINT  DD SYSOUT=*
  //REPORT    DD SYSOUT=*
  //RPTPRINT  DD DSN=xxxxxx.xxxxxx.LOAD,DISP=(NEW,CATLG),
  //          UNIT=SYSDA,SPACE=(CYL,(nn,nn),RLSE),
  //          DCB=(RECFM=FBA,LRECL=nnnnn,BLKSIZE=nnnnn)
  //SYSIN     DD  *
  /LOAD DDNAME=RPTPRINT ID=reportid GEN=nnnnn SEQ=nnnnn
  /*
  //
  
  

• To have your receiving View (SARSTC) collect the reports, run IEBGENER against each of the individual report datasets, with //SYSUT2 DD setup with the CLASS/DEST/FORM that match the SARINIT CLSL, DEST, and FORM parameters of the receiving View database. Execute this IEBGENER job with the reports original jobname, and the reports original SYSOUT ID defined as the value for "reportnm" in the following JCL sample:

  //Origjobname...                          <=== Original reports Jobname
  //STEP1    EXEC PGM=IEBGENER
  //SYSPRINT DD  SYSOUT=*
  //SYSUT1   DD  DSN=xxxxxx.xxxxxx.LOAD,DISP=SHR
  //SYSUT2   DD  SYSOUT=(x,reportnm,vform),DEST=vdest        <=== Modify
  //SYSIN DD DUMMY
  //
  
  

• After collection to the receiving database, run SARBCH /CHANGE, with ARCHDATE=....  against each of the individually collected reports to change the archive date of the report to its original archive date:

  //SARBCH   JOB ...
  //STEP1    EXEC PGM=SARBCH,PARM='view.DB2'         <=== Modify DB name
  //*STEPLIB  DD DISP=SHR,DSN=view.CVDELOAD        <=== Modify, if needed
  //SYSPRINT DD SYSOUT=*
  //REPORT   DD SYSOUT=*
  //SYSIN    DD  *
  /CHANGE ARCHDATE=mm/dd/yyyy GEN=nnnnn ID=reportid SEQ=nnnnn
  /*
  //
   

NOTE - When the ARCHDATE is changed, the GEN and SEQ numbers will automatically reflect the GEN and SEQ numbers of the receiving database's ARCHDATE.

 

• Optionally, run SARBCH /DELETE on the moved reports, if you do not want the reports to remain on the sending database.

//SARBCH   JOB ...
//STEP1    EXEC PGM=SARBCH,PARM='VIEW.DB1'          <=== Modify DB name
//STEPLIB  DD DISP=SHR,DSN=VIEW.CVDELOAD          <=== Modify, if needed
//SYSPRINT DD SYSOUT=*
//REPORT   DD SYSOUT=*
//SYSIN    DD  *
/DELETE ID=reported GEN=nnnnn SEQ=nnnnn
/*
//

 

Additional Information

This knowledge article is not meant to be a one size fits all solution. Depending on your actual requirements and environment, If you are uncertain of what needs to be done for your specific circumstance, it would be best to open a support case and speak with a product Support Engineer.