ROS414TI CA ROSCOE XTPM INTERFACE TERMINATED

Products

• Roscoe

Issue/Introduction

 

How to restart XTPM after it is terminated or hung.

1.  

Environment

Release:
Component: ROSCOE

Resolution

Roscoe creates and manages a z/OS System Address Space (ROSAS) to manage Cross Memory facilities. This address space is an extension of the current Roscoe subsystem. There is 1 ROSAS for each system. ROSAS is started by the first Roscoe which is brought up after an IPL. Usually there is no need to restart it in between IPL's unless it abends.

Instructions:

To restart it, you must start another Roscoe. If this does not work and there is a problem with XTPM being hung or disabled, you will have to bring down ROSAS using the ROSASUTL utility. Here are the steps to do this:

1. Bring down all Roscoe jobs. It should not be necessary to recycle the regions to get the task working again if ALL the Roscoe jobs are down.
   If any Roscoe jobs are running, you will get this message when running the ROSASUTL utility JCL:

     RSASU06E: ROSCOE SYSTEMS ACTIVE REQ IGNORED

   A successful execution will return the following message from the utility:

    RSASU41I: ROSAS HAS BEEN TERMINATED

   The RSASR60 address space can be displayed from the console by issuing

    D A,RSASR60

   on the console.
   
   
2. Change the STEPLIB DD in the ROSASUTL JCL to your RO60LIB.
   
   
3. Run the ROSASUTL JCL to bring down ROSAS

   //JS01    EXEC PGM=ROSASUTL,REGION=4000K 
   //STEPLIB  DD  DISP=SHR,DSN=ROSCOE.RO60.RO60LIB 
   //SYSABEND DD  SYSOUT=* 
   //SYSPRINT DD  SYSOUT=* 
   //SYSIN    DD  * 
   SHUTR60 
   /*

4. Restart all the Roscoe jobs.