Invoking OPS from ISPF returns message REXX exec member OP1FLT10 does not exist in the TSOLOAD search order

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

As we have upgraded OPSMVS R14.0 on a test system.

After the upgrade if we select the options from ISPF , OPS(invoking OPSMVS) =>1( Selection 1 option to invoke OPSLOG) =>PR => F8, we are getting below exec not found -

REXX exec member OP1FLT10 does not exist in the TSOLOAD search order.
***                                                                      

 

Environment

Release : 14.0

Component : OPS/MVS

Cause

Hold actions not executed

Resolution

After the apply of certain PTFs, some OPS/MVS load modules must be refreshed.

Example of instructions that may be contained in those hold actions:

 

           **************************                         
            * STEPS    TO    PERFORM *                         
            **************************                         
                                                               
1. This PTF updates load module OPSAEX, as well as the other   
   load modules identified by the ++MOD statements contained   
   in this PTF.  APPLY of this PTF updates SMP/E Target        
   loadlib CCLXLOAD.                                           
                                                               
2. Copy the updated load modules, panels, and rexx programs    
   from SMP/E Target libraries to any other deployed copies.   
                                                               
3. If the system library lookaside (LLA) program is managing   
   any updated loadlib, you must refresh LLA by using MVS      
   system command "F LLA,REFRESH" or some equivalent           
   mechanism.                                                  
                                                               
4. TSO users must get out of OPSVIEW.                          
                                                               
5. Stop OPS/MVS.                                               
                                                               
6. If the system link pack area (LPA) contains any updated     
   load module, you must refresh LPA by using MVS system       
   command "SETPROG LPA" or some equivalent mechanism.         
                                                               
7. Start OPS/MVS.                                              
                                                               
8. TSO users may access OPSVIEW.  Depending on how OPSVIEW is  
   accessed, this may require TSO logoff/logon.