Best Practices in JCL Management
Understand the issues that must be addressed in every IT organization for production error prevention through the deployment of Best Practices for managing JCL as an asset.
Today’s data center is an increasingly complex environment. Most sites run multiple z OS images: one image for development, another for testing new software, and one or more production images. In many cases, production JCL that can run on any number of images is usually kept in a central repository on a single image. While it is no longer sufficient to check JCL solely on the machine on which the JCL resides, it can be complicated and costly to check JCL in all the environments manually.
JCLplus+Remote provides a powerful and extremely flexible middleware communication method that enables JCL to be sent from a source image to a target image for JCLplus+ syntax checking and validation there, then have the results returned to the source image. This process functions in either online or batch modes and can also enable communication between z OS and other platforms, like Windows or the RDz Eclipse developer environment.
JCLplus+Remote simplifies the management of JCL including syntax checking and validation in complex environments. It allows JCL that resides in one environment to be validated in one or more remote environments. With JCLplus+Remote you can, for example, easily validate the JOBs and PROCs in the production environment from the development environment.
JCLplus+Remote integrates easily with change management procedures to ensure that JCL and PROCs being returned to a production environment will work properly in the production environment.
Access to all JCLplus+Remote features and operations can be controlled and restricted at the user level. All inter-component communications can be encrypted. Nine levels of encryption are supported. In addition, all data transfers can be compressed to conserve bandwidth.
JCLplus+Remote supports both TCP/IP and VTAM APPC protocols for inter-component communications.