Managing Roscoe and Cross Memory (XTPM)

book

Article ID: 38118

calendar_today

Updated On:

Products

CA Roscoe

Issue/Introduction

Summary: 

Managing multiple Roscoe's with XTPM

CA Roscoe XTPM uses MVS cross memory services to transfer data between Roscoe and an external application. The use of cross memory services limits the scope of the application to a single MVS system such as TSO, CICS or another Roscoe. In this document, the discussion will be restricted to transferring data to another Roscoe system.

Background:  

When a site runs unmanaged multiple Roscoes, usually a specific system is the workhorse, logging most of the CPU cycles while the other systems sit idly by. When the system is managed, all Roscoes will have an almost equal number of users. Another reason for using XTPM is to isolate users who run tasks under ETSO that use significant amounts of memory or users that are using Roscoe ETSO for strategic testing.

Instructions: 

Roscoe XTPM communication between the target Roscoe and the external Roscoe system is implemented by an interface module. The installation instructions for this interface module is found in Appendix B of the CA Roscoe Installation Guide. The communication interface module is an Roscoe ETSO application and must be defined by an EPL definition. A sample definition for ROSXROS is found in section B.8.3 of the CA Roscoe Installation Guide.

Using CA Roscoe XTPM is as easy as entering the ETSO call command:

CALL ROSXROS +-userid/password-+ +-ROSID=code-+

The userid and password will default to the user's current security signon userid and password.

The ROSID= should be specified only if the user is to be transferred to a specific Roscoe otherwise the user will be transferred to the Roscoe with the lowest current session count.

There is a central ROSCOE and a number of satellite Roscoes. Each of the satellite Roscoe's ROSID has been defined to the communication interface module either specifically, generically, as a wild card, or it can be totally omitted. When the user issues the call to ROSXROS above, he is transferred either to the CA Roscoe specified in his command otherwise he would be transferred to the CA Roscoe with the lowest current session count. 

In addition to managing the CA Roscoe systems at your site, XTPM will allow a user to bounce from Roscoe to Roscoe using the RCS escape character and RCS escape PF key. See section 10.1.3.1 of the CA Roscoe User Guide for a full description of accessing multiple CA Roscoe systems from a single terminal.

Environment

Release:
Component: ROSCOE