Gen z/OS IT TIRM042E -805 TIRPROFD "NOT FOUND ..." after PTF maintenance

Products

• Gen
• Gen - Host Encyclopedia

Issue/Introduction

After applying CARS 2307 maintenance when try to access the the Gen 8.6 z/OS IT panel  "IEFC1  =   Installation Tool " seeing the following error 

TIRM030E:   APPLICATION FAILED - UPDATES HAVE BEEN BACKED OUT            
TIRM042E:   *** PROFILE ERROR DETECTED ***  9 0001                       
-------------------------------------------------------------------------
DSNT408I SQLCODE = -805, ERROR:  PACKAGE NAME DB2PKG1..TIRPROFD.1B3BF-  
         4CD0F627B88 NOT FOUND IN PLAN IT86CS1. REASON 03                
DSNT418I SQLSTATE   = 51002 SQLSTATE RETURN CODE                         
DSNT415I SQLERRP    = DSNXEPM SQL PROCEDURE DETECTING ERROR              
DSNT416I SQLERRD    = -251  0  0  -1  0  0 SQL DIAGNOSTIC INFORMATION    
DSNT416I SQLERRD    = X'FFFFFF05'  X'00000000'  X'00000000'              
         X'FFFFFFFF'  X'00000000'  X'00000000' SQL DIAGNOSTIC            
         INFORMATION                                                     
-------------------------------------------------------------------------
TIRM046E:   *** TRANSACTION PROCESSING TERMINATED  IEFC1                 
TIRM044E:   *** PRESS PA2 TO CONTINUE *** 

Environment

Release : 8.6

Resolution

The user resolved the -805 error by binding the package TIRPROFD. 

Support received feedback from Gen Engineering per below:
===
The PTFs included in CARS2307 should have had no impact on the TIRPROFD module. Engineering suspects the problem actually occurred when some earlier PTFs were applied.
 
From the reported error message, Engineering can see you are running with the TIRPROFD module that was provided in 2021 with the Upgrade PTFs (UPGRADE C, C++, COBOL AND DB2 FOR GENERATORS AND RUNTIMES - LU01883, LU01884, LU01885, LU01886, LU01887, LU01888, LU01889, and LU01908). Engineering's suspicion is that the HOLDDATA steps may have been missed when PTF LU01884 was applied.
 
This can be confusing because the z/OS IT is a Gen-generated application itself and the TIRPROFD module actually needs to be bound twice, as described in the steps below:
 
1. The TIRPROFD DB2 Package used by the z/OS IT needs to be bound using the IT's Collection ID (stored in the TIXECOLL ISPF variable in the TIUIT2 PARMLIB member). NOTE: this bind should be done on the DB2 subsystem where the z/OS IT executes.
 
To perform this DB2 Bind Package, the HOLDDATA in PTF LU01884 contained the following instructions:
                      **************************                        
                      * STEPS    TO    PERFORM *                        
                      **************************                        
                                                                       
 1. Modify the PTFBINDI job in the Install JCL dataset to specify      
    'TIB01885' as the input clist. Ensure the Collection ID matches the
    ISPF variable TIXECOLL in PARMLIB member TIUIT2.                    
 2. Submit the PTFBINDI job to re-bind the affected DB2 packages.       
 
 
2. The TIRPROFD DB2 Package used by your generated applications needs to be bound using the IT's Gen Runtime Collection ID (stored in the TIXERTCO ISPF variable in the TIUIT2 PARMLIB member). NOTE: this bind should be done on all DB2 subsystems where your generated applications execute.
 
To perform this DB2 Bind Package, the HOLDDATA in PTF LU01885 contained the following instructions:
                      **************************                        
                      * STEPS    TO    PERFORM *                        
                      **************************                        
                                                                       
 For the Host Encyclopedia:                                            
  1. Ensure the Collection ID matches ISPF variable TIXERTCO in PARMLIB
     member TIUHE2 for jobs CEJOB14R and CEJOB15R in Install JCL        
     dataset.                                                          
  2. Submit the CEJOB14R job to run package bind clist for application  
     runtime DBRM TIROLBCM.                                            
  3. Submit the CEJOB15R job to run package bind clist for application  
     runtime DBRM TIRPROFD.                                            
                                                                       
 For the Implementation Toolset:                                        
  1. Ensure the Collection ID matches ISPF variable TIXERTCO in PARMLIB
     member TIUIT2 for jobs ITJOB07R and ITJOB08R in Install JCL        
     dataset.                                                          
  2. Submit the ITJOB07R job to run package bind clist for application  
     runtime DBRM TIROLBCM.                                            
  3. Submit the ITJOB08R job to run package bind clist for application  
     runtime DBRM TIRPROFD.                                             
 
  
As mentioned earlier, Engineering suspects the HOLDDATA steps documented in PTF LU01884 may have been missed.  The PTFBINDI job should have been customized to use TIB01885 as the input clist and then the PTFBINDI job should have been submitted.
===

Gen Engineering also recommends binding only the packages affected by the PTF.  While it should not cause a problem to bind all packages again, they feel less risk is involved if only the packages affected by the PTF are rebound. Also in the HOLDDATA instructions a clist named TIBxxxxx is always provided (where xxxxx is some number) that contains the necessary bind statements for any packages affected by that PTF.