CA 7 Upgrade 11.3 to 12.1 Datasets UCC7LOGP, UCC7CMDS, UCC7STAT, UCC7CKPT, BROWSE, NCF.COMMDS and NCF.UDQDS

book

Article ID: 205446

calendar_today

Updated On:

Products

CA Workload Automation CA 7 Edition Automic Automation Intelligence CA Unicenter Job Management Option CA Workload Automation iDash

Issue/Introduction

CA 7 datasets when upgrading from release 11.3 to release 12.1:

UCC7LOGP, UCC7CMDS, UCC7STAT, UCC7CKPT, BROWSE, NCF.COMMDS and NCF.UDQDS

I decided that I go with new versions of the above datasets which is what I did when performing the Test upgrade on our Test system. After the upgrade some batch jobs failed because they didn't reference the new COMMDS dataset because I changed the name of this dataset to something like COMMDS.R121. The reason for using a new dataset name like COMMDS.R121 is because in a SYSPLEX environment where we have more than one JES3 GLOBAL in the SYSPLEX the COMMDS dataset is called that same in both environments and I can't rename the COMMDS in on JES3 environment to COMMDS.OLD because it's in use by another JES3 GLOBAL system in the SYSPLEX. To overcome this 'dataset allocated' problem it brings me back to the question of can I use the current R11.3 datasets with r12.1. I believe I can and if so I should be starting CA7 r12.1 with a TYPE=ERST instead of a TYPE=CKPT. If is stick to new datasets with a suffix of '.R121' then there are lots of ACF2 rules that need to be added as well and this is what I want to avoid. By using the same datasets I avoid the 'dataset already allocated' issue and I avoid adding lots of new ACF2 dataset access rules for the new datasets. 

 

Environment

Release : 12.1

Component : CA-7

Resolution

You can use your R11.3 files. When you cut-over from r11.3 to 12.1, you will want to do it at a time after all jobs for r11.3 have completed. Then, after the conversion process for r12.1 is validated and completed, you can start CA 7 r12.1 with a TYPE=ERST if you are reusing the Checkpoint File from r11.3.

This assumes you are not going to go back to r11.3.
Technically, the data in some of the files in r11.3 that are currently in sequential files are now in tables and rows in Datacom and the formatting is different. The conversion utility you are using make is possible to take your data from r11.3 and convert it from sequential and vsam files to tables in datacom. This cannot happen from Datacom using r12.1 data, because there is not conversion backward process.

Even if you were to use different files in r12.1, you would still have the same issue. You have no way to go back. If you retain your files in r11.3 and use new files in 12.1, at least you have data that you can use in back in 11.3, although there would be a gap in the processing. So your testing would be fine, because in a test scenario, it would appear to be fine, but months into processing with 12.1, makes it not realistic.

UCC7LOGP, UCC7CMDS, UCC7STAT, UCC7CKPT, BROWSE, NCF.COMMDS and NCF.UDQDS.

The above files will not impend your falling back to r11.3, since they are of the same format.

Also, if you fall back, you will not have to IPL, because CA 7 12.1 and 11.3 are compatible.

Please retain your r11.3 database. We do not want you to go back to 11.3, but if you do, it would be in your best interest to contact our Support first.