Milestone 12: Starting the Started Tasks

This milestone invokes the Code Pipeline Started Tasks.

Memory considerations

Code Pipeline needs to run in LE 31-bit memory mode. If you know you are running in LE 31-bit memory mode, then nothing additional needs to be done to CM.

If you are unsure of the default Language Environment (LE) settings, you can do the following to determine what you have. You will need to add a CEEOPTS DD card to the CM proc. An example of a suitable data set would be the one that holds their SDEFREFR member.

The member should contain the following:

This will cause LE to write out all the options and memory usage statistics for every subtask that uses LE to DD SYSOUT. (It will dynamically allocate this DD.)

Add the DD, stop CM, start CM, remove the DD after data is captured, stop CM, and start CM.

The output will include information for about 60 settings. Two of these are key: ALL31 and STACK. Here is an example of what you might see in the captured data for these two parameters:

If you see ALL31(OFF) or BELOW as a STACK parameter, you are running in 24-bit memory mode. You will need to add ALL31 and STACK parameters to the CEEOPTS member. Specify ALL31(ON) and make sure the STACK parameter matches the settings displayed in the report—but with BELOW replaced by ANYWHERE.

When you are done determining what your settings are, RPTOPTS(ON) and RPTSTG(ON) can be removed because they are no longer needed.

Task 12.1 Start the CM

Start the CM Started Task as follows:

1. Access the SDSF facility (or whatever spool reader product you normally use).
2. In the COMMAND INPUT field, type the following (where CM PROC Name is the name of your CM procedure), and press Enter:
   /S CM PROC Name
   Job output for a successful invocation of the CM task is shown in the following figure. Make sure the following message indicates that the Code Pipeline Server is running APF-Authorized in the following figure. Various log and trace messages are turned on by the default settings in the SDEFISPW input cards.

CM Invocation Job Output

Starting CM Without an SAF Class Defined

If the SAF Class has not been defined, CM will still be operational but with no internal security. The messages shown in the following figure will be displayed.

CM SAF class message

Task 12.2 Start the CI

Start the CI Started Task as follows:

1. Access the SDSF facility (or whatever spool reader product you normally use).
2. In the COMMAND INPUT field, type the following (where CI PROC Name is the name of your CI procedure), and press Enter:
   /S CI PROC Name
   Job output for a successful invocation of the CI task is shown in the following figure.

CI Invocation Job Output

Task 12.3 Start the CT

Start the CT Started Task as follows:

1. Access the SDSF facility (or whatever spool reader product you normally use).
2. In the COMMAND INPUT field, type the following (where CT PROC Name is the name of your CT procedure), and press Enter:
   /S CT PROC Name
   Job output for a successful invocation of the CT task is shown in the following figure.

CT Invocation Job Output

The highlighted message is only written when the CT task has established communication with the CM task. If this message does not appear, there is a problem with the communications setup and definition.

The final message indicates that the CT Task has communicated with CM and retrieved a list of Warehouses that it manages. If this message does not appear after a few seconds, it may be possible that the Code Pipeline definitions for M.SV and M.WH are incorrect. Correcting these can be done through the Code Pipeline Client after Start the CT, after which the CT Task needs to be re-cycled.

Task 12.4 ISPF dialog

The objective of this task is to be able to invoke the Code Pipeline TSO/ISPF Client in a quick way for the install process. Each Installation should review how they invoke ISPF Applications and change this invocation as necessary.

Panel invocation

Code Pipeline can be invoked directly from a panel, specifying the appropriate configuration name. The following table is an example of different invocations based on the sample WZZRCCNF member delivered:

To quickly see whether Code Pipeline is setup correctly, before the panel option is added it is possible to type TSO WZZRCSPF ISPT (where ISPT is the configuration name defined in the table earlier).

Successful invocation

If the Code Pipeline invocation works successfully, a Code Pipeline welcome screen will appear for the first invocation as shown in the following figure.

Code Pipeline Welcome screen

Once your name is entered, the Code Pipeline main menu will appear as shown in the following figure.

Code Pipeline Main menu

Once this screen is displayed, you have connected to the Code Pipeline Server.