APAR RO93218 provides JCL to select 'orphaned' VRM active records.

Document ID : KB000005139
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

APAR RO93218 provides JCL to select 'orphaned' VRM active records.  An orphaned record is one that is still on the active VRM chain even though its corresponding job is not currently in CA 7's 'queues'.  

If either SELECT statement returns data, a DELETE must be done externally (not a CA 7 command) using SQL.

Resolution:

APAR RO93218 provides JCL to select 'orphaned' VRM active records.  An orphaned record is one that is still on the active VRM chain even though its corresponding job is not currently in CA 7's 'queues'.  The provided JCL has two select statements--one for selecting orphaned records for a CA 7 job number that is not currently being used and the second one if for orphaned records where the CA 7 job number is currently in the 'queue' but with a different job name than the one on the current active VRM record.

If either SELECT statement returns data, a DELETE must be done externally (not a CA 7 command) using SQL. For example the following output was received from running the provided SELECT.  Note that the R.DB must be the client's logical database name (as pointed to by DBPARMS):

INPUT STATEMENT:

  SELECT JOB, CA7#

  FROM CA7_ACT_JOB_RES R

  WHERE R.DB = 'CA7770'  AND

  NOT EXISTS

  (SELECT *

  FROM CA7_QUEUE Q

  WHERE Q.DB = R.DB         AND

        Q.JOB = R.JOB)

  GROUP BY JOB, CA7#;

  

  JOB             CA7# 

  ________ ___________ 

  LU37FSTA        2761 

  ___ 1 row returned ___

 

This row must be deleted with the following SQL input:

 

DELETE 

FROM CA7_ACT_JOB_RES 

WHERE DB = 'CA7770' AND 

JOB = 'LU37FSTA' AND 

CA7# = 2761; 

 

You will have a DELETE statement for each row that shows in the SELECT output. Many times the two SELECT statements will show the same jobs/same job numbers and that's OK--they only require the one DELETE statement for each job/job number combination.  If the second SELECT shows job(s) not listed from the first SELECT statement then you will have to provide a DELETE statement for each different job also.

After applying RO93218 and running the DELETE you should not have any more 'orphaned' VRM records.

Additional Information:

If you have any questions on the above procedure please contact CA 7 support.  The SQL DELETE statement is working on the CA 7 database and does delete records--so if you are not sure, please contact us and provide the output from the SELECT statements.