CA Gen 8.5 - Tips for Installing PTFs With SAMPJCL
search cancel

CA Gen 8.5 - Tips for Installing PTFs With SAMPJCL

book

Article ID: 56591

calendar_today

Updated On:

Products

Gen Gen - Workstation Toolset Gen - Host Encyclopedia Gen - Run Time Distributed

Issue/Introduction

Installing PTFs with SAMPJCL is sometimes confusing for CA Gen customers. In this document we provide some tips to clarify the process and some tips we find useful.

1.      After creating your CSI (GEN3CSI job) and before receiving any PTFs (GEN7RECP job), you should increase the size of your SMPPTS dataset.  It is recommended that the size of   the SMPPTS dataset be increased to approximately 4000 tracks for the primary extent with a large secondary extent specified.  Some of the Gen r8.5 PTFs are very large and the increased size of the SMPPTS dataset will help to prevent receive problems.

 

2.      If your SMPPTS dataset runs out of space after you have received some PTFs, make sure the existing SMPPTS dataset is NOT deleted before its contents are copied across to the new, larger SMPPTS dataset.

 

3.      If the SMPPTS dataset runs out of space while receiving PTFs and your site has an automatic recovery program that attempts to increase the size of the SMPPTS dataset, the results can be unpredictable and may not work successfully even though you get a return code of zero.  Incomplete receive processing could show up as link edit errors when you execute the PTF apply job.  The link edit errors will indicate that modules are missing. You may need to reject the incomplete PTF and then re-receive and re-apply it.  Following are some examples of the type of link edit errors that you might see: 

GIM23911E ** LINK-EDIT PROCESSING FOR SYSMOD RO61936 FAILED FOR MODULE ABSYMTAB IN LMOD TICPMGNX IN THE SMPLTS LIBRARY.
   THE RETURN CODE (12) EXCEEDED THE ALLOWABLE VALUE. DATE 15.044 - TIME 10:56:47 - SEQUENCE NUMBER 000009 - SYSPRINT FILE SMP00010.

GIM23912E ** LINK-EDIT PROCESSING FOR LOAD MODULE BUILD PROCESSING FAILED FOR MODULE ABSYMEV IN LMOD TICPMGNX IN THE SMPLTS LIBRARY.
   THE RETURN CODE (12) EXCEEDED THE ALLOWABLE VALUE. DATE 15.044 - TIME 10:56:47 - SEQUENCE NUMBER 000009 - SYSPRINT FILE SMP00010.
    

4.      You can verify the status of the PTFs that you have received by running a SMP/E report of your CSI to list what SYSMODS have been received. This is an example of JCL that can be used to run a SMP/E report:

//**********************************************************************
//* List SYSMODS for CSI
//**********************************************************************
//*
//LSYSMOD   EXEC PGM=GIMSMP,PARM='DATE=U',REGION=0M
//*** CHANGE TO YOUR CSI DATASET NAME ***
//SMPCSI    DD DISP=SHR,DSN=YOURCSI.R85.CSI
//SMPCNTL   DD   *
SET BOUNDARY(CAIT0) .
LIST SYSMODS  .
/*
//*
 

5.      CA GEN INTERIM ENHANCEMENT #1 PTFs RO73021 and RO73022 require 2 new datasets: SCEEBIND and SCEEBND2. These datasets must be added to each CSI via DDDEF statements before the PTFs are applied.  PTF RO70569 introduces CEHBSAMP member IE1DDDEF that contains sample JCL to do this. Here is an example of the JCL used to add a DDDEF to your CSI:

//**********************************************************************/
//* MEMBER: IE1DDDEF                                                
//**********************************************************************/
//*                                                                   
//* THIS MEMBER CONTAINS JCL AND CONTROL STATEMENTS TO ADD NEW DD  
//* DEFINITIONS TO AN EXISTING CSI. ONLY RUN THIS JOB IF THE DATASETS 
//* MENTIONED ARE NOT YET DEFINED IN THE CSI.                         
//*                                                                   
//* CUSTOMIZE THIS JOB FOR YOUR ENVIRONMENT. MAKE THE FOLLOWING 
//* CHANGES BEFORE YOU SUBMIT THE JOB:                              
//* 1.ADD A JOBCARD.                                                  
//* 2.CHANGE CAI.CAGEN.CSI TO MATCH THE NAME OF YOUR CSI.             
//* 3.CHANGE BOUNDARY NAME IF NOT CAGENT. THIS IS THE CSI TARGET.     
//*                                                                   
//*                                                                   
//* THIS CHANGE SHOULD BE DONE REGARDLESS OF WHETHER CSM OR SAMPJCL IS
//* THE METHOD USED TO APPLY CA GEN MAINTENANCE. IT NEEDS TO BE DONE  
//* BEFORE THE INTERIM ENHANCEMENT #1 (IE1) PTFS ARE RECEIVED AND     
//* APPLY'D.                                                          
//*                                                                   
//**********************************************************************/
//STEP01   EXEC PGM=GIMSMP,PARM='DATE=U'
//*** YOUR CSI DATASET NAME
//SMPCSI   DD DSN=CAI.CAGEN.CSI,DISP=OLD
//SMPCNTL  DD *
 SET BOUNDARY(CAGENT).
 UCLIN.            
 ADD DDDEF(SCEEBIND)   SHR DA(CEE.SCEEBIND) .
 ADD DDDEF(SCEEBND2)   SHR DA(CEE.SCEEBND2) .
 ENDUCL.
/*
//*

 

6.      Anytime you are going to receive additional PTFs, you should re-run job GEN1HOLD to download the most recent copy of the CA error and fixcat HOLDDATA and then re-run job GEN7RCH to receive the HOLDDATA.

 

7.      For PTF apply job GEN8APYP, you will need to add a BYPASS command for any PTFs that have HOLDDATA instructions. This is an example of the BYPASS command you can use in the GEN8APYP job for the Gen 8.5 PTFs:

BYPASS(HOLDSYS(ACTION AO DEP DOC DB2BIND DELETE) HOLDCLASS(ERREL))  .

 

8.      It is recommended that you always use the CHECK command when running the GEN8APYP job.  After successful completion of the GEN8APYP job, re-run with the CHECK parameter removed.

 

9.      It is recommended that you do not run job GEN9ACCP because after you run this job you will not be able to back out any PTFs from your CSI.

 

 

For more information about SMP/E, please see the IBM publication, 'SMP/E for z/OS User's Guide'.  The IBM SMP/E Version 3 documentation can be found here:

 

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.gim/gim.htm.

 

Environment

Release: KGNDDL99000-8.5-Gen-DBP Developer License
Component: