Installing the z/OS agent#
Before you deploy to the IBM® z/OS® platform, you must install the z/OS agent and configure the z/OS server for communication with HCL Launch. If the build process runs on a different logical partition (LPAR), then you must additionally install the agent on the build LPAR. You can install the z/OS agent and deployment tools by using the HCL® System Modification Program Extended (SMP/E) or by extracting archive files to the z/OS UNIX™ file system.
Note: Beginning with version 6.2.4. the z/OS deployment tools have become part of the z/OS agent. The deployment tools no longer require a separate installation. If you are upgrading from a version earlier than 6.2.4, see Upgrading IBM z/OS agents for details about the changes.
Review the system requirements, and then plan the installation:
- Review Choosing a CodeStation and planning storage.
- Review Security requirements on IBM z/OS computers.
- Review ISPF client gateway requirements.
To install the agent by using SMP/E, complete these steps:
Install the z/OS agent by using SMP/E. See Installing the z/OS agent and deployment tools by using SMP/E.
Install agents from the command line. See Installing agents from the command line, and start with step 3.
To install by extracting files to the z/OS UNIX file system, see Installing agents from the command line.
Deploying by using the Job Monitor
You use the Job Monitor to submit jobs and to monitor the job status in your deployment. You must ensure that you have a Job Monitor task running and that you run the Urban Code Deploy process to submit or to monitor the job. Then, you must set up Job Monitor connection properties in your HCL Launch environment.
- Installing the binary and config files to different directories
By default, the agent installer installs the binary and config files into the same directory. You can customize the installation so that these files are installed into different directories. Also, multiple agent configurations can share the same copy of binary files which makes security control and product upgrading easier.
Parent topic: z/OS considerations for UrbanCode Deploy