Remote Server Basics
This section explains the fundamental concepts that apply to z/OS Code Pipeline Remote Servers.
Execution Environment
The Server runs as an MVS Started Task.
Installation
See the Code Pipeline Installation and Configuration Guide for details, and follow the instructions for the setup of a CT Started Task.
Entry in CMSC PARMLIB Member
Every z/OS Remote Server must be reflected by a PARMLIB member entry for the BMC AMI Common Mainframe Services Controller (CMSC). For a discussion of PARMLIB configuration, see Common PARMLIB Information in the Code Pipeline Overview section of the Code Pipeline Installation and Configuration Guide. For installation details, see Task 8.6 Generate Started Task PARMLIB Members.
Method of Communication
Remote Servers establish a direct connection with the Code Pipeline Master Server ISPWCM. Remote Servers also accept requests directly from Code Pipeline Clients.
The following figure depicts the various Remote Server connections:
Remote Server Startup Process
When a Remote Server starts, the processing described in the following table takes place:
Sequence | Description |
|---|---|
1 | Read the applicable PARMLIB member. |
2 | Establish a connection and log onto Code Pipeline using the values in the PARMLIB member. This connection will remain open for requests that originate from the Code Pipeline Master Server (ISPWCM). |
3 | Server definition parms (defined in M.SV) are returned, which include the port number to listen on for requests coming directly from other Code Pipeline processes, including Code Pipeline CT and Remote Servers. |
4 | Listen on port defined in M.SV for remote requests. |
Local Warehouse
Each Remote Server has the capability of storing components in a local warehouse.
Code Pipeline
’s Deploy feature uses the warehouse to stage components prior to them being implemented. The z/OS warehouse is a PDS/E implementation.
Spawning Processes
Remote Servers have the ability to spawn processes for Deploy Operations. These processes run independently of the Remote Server and communicate back to CM the status of the implementation or activation. The mechanisms by which the processes are spawned is a z/OS Started Task. The Remote Server issues the MVS START command. The task will run under the authority of the UserID associated with the Started Task.
Resiliency
If the BMC AMI Common Mainframe Services Controller (CMSC) fails or goes down, it is not necessary to shut down and restart any of a
Code Pipeline
Remote Server’s started tasks. PARMLIB member entries for the CMSC are stored in memory and continue to be used.
M.SV Entry
The Code Pipeline Maintenance option M.SV is used to define Remote Servers, and all Remote Servers must be defined here. The M.SV entry screen is shown in the following figure.
Command ===>
Enter required details:
Server Name (KEY) ==>
System Type ==> MVS (MVS/WIN/AIX/LINX/SUN/HPUX)
Server Type ==> (CT/CI/RS/CM)
Address ==> (CT/RS Only)
Socket ==> (CT/RS Only. Restart CT/RS if changed)
CSS Socket ==> (CT Only. Restart CT if changed)
Deploy ==> (Y/N CT/RS Only)
Encryption ==> (CT Only. Workbench session encryption type)
Cross-memory ID ==> (CT Only. Cross-memory ID)
Description ==>
Press ENTER to complete the change or END to terminate
Note: To add a new entry the Key must be unique
See the Code-Pipeline-Technical-Reference-Guide for a description of the input fields. The Address and Socket should be specified for z/OS Remote Servers.