This plug-in simplifies IMS operations in support of application deployment by issuing IMS commands. The plug-in integrates into the IBM UrbanCode Deploy design process, allowing you to automate application deployment for continuous delivery in an agile environment.
For detailed usage information, including IMS Application Deployment example, see Usage.
This plug-in requires agents that run on the z/OS platform. For more information, see:
- Installing servers and agents
- Installing the z/OS deployment tools
- Deploying to the z/OS Platform
The plug-in includes the Execute IMS Command step that can be used to submit IMS operator commands to members of an IMSplex. This step can be added to your application deployment process by issuing the UPDATE PGM command.
This plug-in requires version 6.1 of IBM UrbanCode Deploy.
No special steps are required for installation. See Installing plug-ins in UrbanCode Deploy.
IMS information resources:
Troubleshooting information for the IMS plug-in
Tip: For more questions and answers, see the UrbanCode forum on IBM developerWorks.
Error messages and reason codes
If IMS commands return error messages or return codes, they are displayed in the output properties and in the output log.
IMS troubleshooting information resources:
Using the IMS plug-in in UrbanCode Deploy
This IMS plug-in allows execution of IMS type-1 and type-2 commands. You can use this plug-in for various scenarios where IMS commands are traditionally used, but a common scenario that takes advantage of UrbanCode Deploy is IMS application deployment. See Deploying IMS application programs below for an example.
The following information assumes basic knowledge of UrbanCode Deploy and its user interface.
Before you begin
- Ensure the IBM UrbanCode Deploy server and the z/OS deployment tools are installed.
- Ensure the IMS plug-in is installed.
Setting up resources for IMS application programs
In UrbanCode Deploy:
- In the Resources tab, create a top-level group.
- Within the top-level group, create agents for each IMS subsystem.
- Under each agent, add the components that correspond to your application programs. For more information about how components are used in Urban Code Deploy, see Creating components.
Process development using the IMS plug-in
To start using the IMS plug-in, create a new or edit an existing UrbanCode Deploy process.
In order to include IMS plug-in steps in the process, locate the IMS entry in the Steps Palette:
Drag and drop the Execute IMS Command step onto the process editing screen.
Configuring IMS plug-in properties
When the Execute IMS Command step is added to a process, the Edit Properties dialog opens. Provide the following required parameters specific to the IMS plug-in:
||The IMS command to issue, followed by parameters. For example:
||IMS ID is used to identify the target IMS system the command is directed to within a given IMSplex. It consists of four alphanumeric characters (for example, IMS1).
An easy way to find the IMSID is to access a z/OS console (MCS or EMCS) and look for the following message:
||The 1-to-5 character suffix of the IMSplex name. An IMSplex is defined as multiple IMS systems that cooperate with each other in a z/OS Parallel Sysplex environment to process a common shared workload. The following QUERY command can be used to determine the IMSPLEX name suffix (last 5 characters under the IMSPLEX field), assuming you have access to an authorized IMS SPOC console:
||Name of a z/OS library that contains the IMS nucleus and all the action modules necessary to run IMS and its utilities.
The RESLIB name is usually identified in the JCL that is used for starting an IMS procedure with the DD named DFSRESLB or in the parm RESLIB= in the IMS procedure used to start IMS.
Example properties for the Execute IMS Command step:
Deploying IMS application programs
For the deployment processes to work, it is assumed that the UrbanCode Deploy agents are installed in the UNIX System Services side of IMS.
There are many possible ways to create processes for IMS application deployment. Process steps may differ depending on IMS environment setup, application details, and others. For example, under certain conditions, an existing application can be redeployed by a process that stops the run-time application, deploys a new version of application data sets, and restarts the application. The following example demonstrates how an UrbanCode Deploy process might look like for such a scenario:
In this example, the IMS Plug-in is used twice. First, it is used to stop existing application by executing the
UPDATE PGM NAME(name) STOP(SCHD) command. The plug-in parameters for this step might look as follows (the actual parameter values will be specific to your environment):
Then, after the data sets for the new version of the application are copied into the system, the IMS plug-in is used to start the application by executing the
UPDATE PGM NAME(name) START(SCHD) command. The plug-in parameters for this step might look as follows (the actual parameter values will be specific to your environment):
- Execute IMS Command
Allows execution of IMS type-1 and type-2 commands.
||String||IMS command, followed by parameters. For example: UPDATE PGM NAME(name) START(SCHD)||Yes|
||String||A 4-character IMS ID name used to identify the target IMS system the command is directed to within a given IMSplex.||Yes|
||String||The 1-to-5 character suffix of the IMSplex name.||Yes|
||String||Name of a z/OS library that contains the IMS nucleus and all the action modules necessary to run IMS and its utilities.||Yes|
||String||Maximum number of lines to display in the log.||No|
||String||Fail the step if return code is greater than the maximum return code.||Yes|
||String||The output data set to display in the log. Use a comma to separate multiple
data sets. Specify ALL for all data sets.
||String||Number of seconds to wait for the command to complete before terminating.||No|
||Boolean||Whether to wait for the command to complete. If Wait for Command is unchecked, the input for Timeout,
Show Output, Max Lines, and Max Return Code are ignored.