search cancel

CA 7 upgrade 11.3 to 12.1 - conversion process (Job AL2DCV10) - receives message Missing from reverted file

book

Article ID: 212928

calendar_today

Updated On:

Products

CA 7 Workload Automation

Issue/Introduction

Run the last job in the conversion process (AL2DCV10) and it has ended as expected with discrepancies. It has ended with '0040 VRMZ' discrepancies which I can safely ignore but it has also ended with "Missing from reverted file" messages for "JBM1 CAPG8E01" and "JBM1 GIWG8E03". These are due to the fact that when I ran the job AL2DCC10 job to take a backup of the R11.3 database it produced the following messages for these two jobs : 


BK03.302 - BAD MEMBER ENTRY FOR KEY=CAPG8E01 , DSTYPE=JOB, INVALID BLOCK HAS BEEN WRITTEN
BK03.302 - BAD MEMBER ENTRY FOR KEY=GIWG8E03 , DSTYPE=JOB, INVALID BLOCK HAS BEEN WRITTEN

Can these be ignored now for AL2DCV10 before we bring up CA 7 Release 12.1?

 

Environment

Release : 11.3

Component : CA-7

Resolution

**Currently upgrading CA 7 Pre-Production System from 11.3 to 12.1.

**Reviewed the two jobs called CAPG8E01 & GIWG8E03….

Job AL2DCV10 shows errors…

Missing from reverted file

      JBM1 CAPG8E01

Missing from reverted file

      JBM1 GIWG8E03

**From Previous CA 7 case 32637275, I advised customer that these two jobs called CAPG8E01 & GIWG8E03 do not go with any defined Schedule.

**Explained to the customer that we can try and redefine these job names in 11.3, but it will not allow access to the missing schedule data. Sustaining Engineering (Level2) can use CA 7 zap commands to associate these job names with the orphaned schedules,  and then purging the jobs.

**Explained to the customer that another option is to leave it,  override the validation error, and then delete the jobs/schedules after they come up on release 12.1.

**Customer explained that these jobs are not know to the Production Schedule Team,  could be old jobs that someone run in an old schedule.

**Also verified that the customer did not receive any errors reported when they ran the 11.3 database verification against this SASSBK00 which was job AL2DCB10.

**Customer continued with the upgrade and ignored these two jobs