How to continue processing jobs with Deliver while the View database is unavailable?

Products

• Deliver
• View

Issue/Introduction

Jobs processing with Deliver when the view database is not available.

Resolution

When you want Deliver to continue to process jobs while the View database is unavailable, you can dynamically change the ARCH parameter in the RMOPARMS member to use a different ARCHn statement as the default using an operator command.

For this process to work, the ARCH field on the all the Report Definitions that archive “Direct to View” must be blank.  This means the Report Definition will use the default ARCH value found in the RMOPARMS member when selecting the archive statement for the report. 

Example:
  ARCH=1
  ARCH1=DIRECT/VIEW/SYSTEM1 where VIEW.SYSTEM1 is the database name

Set-Up

1.  Set the SETCMD parameter in the RMOPARMS member to YES.  This parameter must be changed to YES prior to the Deliver started task being started. Once this parameter is set to YES, you can issue SET commands to change the following parameters without stopping the Deliver started task.  

2.  Create an ARCHn statements that will send the output to a Jes class specified by the CA View initialization parameter, CLSL. 

Example:  
In the RMOPARM dataset ARCH1 is the default for archival of all reports with a blank in the ARCH field on the Report Definition panel.  We assume View is picking up class B.

ARCH=1                                                      
ARCH1=DIRECT/VIEW.SYSTEM1                               
ARCH2=B///D                                                 
.                                          
.
.                                             
SETCMD=YES      

The SETCMD parameter allows dynamic changing of the ARCH= variable. Parameter must be set to 'YES' and the CA Deliver task recycled prior to issuing 'SET' commands.
 
           The format of the SET command is       F RMOSTC,SET ARCH=2
                                                  
When we change the ARCH parameter in the RMOPARMS with a SET command, we can cause all the reports to use the new ARCH2 Statement that will send the report to Jes in class 'B' while CA View is unavailable. 

When we are finished upgrading the CA View database, issue the SET command  again to change ARCH=2 to ARCH=1.  Now, new reports will again be written directly to the CA View database.  When SARSTC is started, it will pick up the reports waiting in Jes class 'B'.    

Example:

         In View:

           1. Assume the started task picks up class B: CLSL=B  

         In  Deliver:

           1. Set SETCMD=YES
           2. Create the following ARCH2 tatement: ARCH2=B///D                                                 
                       
When the View database becomes available, the ARCH parameter can be changed back to  its original value with another SET command.             

F RMOSTC,SET ARCH=1