PUT2PROD EXEC

Purpose

The PUT2PROD EXEC performs the actions listed in the systemid $PRODS file for the z/VM components, features, or products that are installed on the z/VM system.

Operands

ALL

specifies that products serviced using the SERVICE command will be put into production.

compname

is the 1- through 16-character alphanumeric component name identifier for the component to be put into production. Specify the component name as it is on the :PRODID tag in the VM SYSSUF table.

SAVECMS

specifies that the CMS saved systems will be built and put into production.

SEGMENTs

specifies which segment or segments will be put into production. If SEGMENTS is specified, it must be followed by ALL or by one or more segment names.

ALL: when specified with the SEGMENTS option, all segments defined in the system segment build list (SEGBLIST EXC00000) will be built and put into production.
segment_name: specifies one or more segment names that will be put into production.

Usage Notes

The PUT2PROD EXEC will affect your production environment. The following production environment virtual machines will be logged off in order to update minidisks or SFS directories they own:
- DIRMAINT
- TCPMAINT
The PUT2PROD EXEC must be executed from the default MAINTvrm user ID or equivalent.
The PUT2PROD EXEC processes components, features, and products that provide a :P2P. section in their PPF.
A BLDCMS user ID and a BLDSEG user ID must exist.
When the PUT2PROD EXEC is used to build CMS saved systems (whether overtly with the SAVECMS operand or in conjunction with product service processing), the SSI relocation domain for the MAINTvrm user ID is modified, when necessary, to that of the current member system. The updated relocation domain remains in effect upon completion of the PUT2PROD EXEC.

Examples

To put all components, features, and products that were serviced (have an entry in the SERVICE $PRODS file) into production enter:
```
  PUT2PROD
```
or
```
  PUT2PROD ALL
```
To put only TCPIP into production, enter:
```
  PUT2PROD TCPIP
```
To put only the CMS saved systems into production, enter:
```
  PUT2PROD SAVECMS
```
To put only the XXXX and YYYY segments into production, enter:
```
  PUT2PROD SEGMENTS XXXX YYYY
```

Input and Output Files

Input Files
ppfname PPF: The usable form product parameter file.
VM SYSSUF: The system-level service update facility table.

Input/Output Files
VM SYSPINV: The system-level Product Inventory table, which specifies which products are installed on which systems or members.
systemid $PRODS: The put into production file that is a list of products and associated objects that were serviced for the system.
SERVICE $PRODS A: The put into production file that is a list of products that were serviced using the SERVICE EXEC.
PUT2PROD $CONS A: The console listing for the current invocation.
$VMFP2P $MSGLOG A: The PUT2PROD message log.

Output Files
prodid SRVPROD: The service-level production status table.
VM SYSPINV: The service-level product inventory table.

Messages and Return Codes

For a complete explanation of each message, use the HELP Facility to view the message explanation online or see the appropriate messages documentation. To display information on a specific message, for example VMF002E, enter:

help msg vmf002e

If you are unfamiliar with the z/VM HELP Facility, enter help to display the main HELP Menu. For information on the HELP command, enter:

help cms help

Module Identifiers for VMSES/E Messages shows the format of VMSES/E messages and lists the identifiers for each VMSES/E exec.

PUT2PROD issues the following return codes:

Return Code	Explanation
0	Command completed successfully.
2	Command completed successfully but extraneous data was encountered.
4	Command completed with one or more warning conditions.
12	Command failed because of an internal error.
24	Command failed because of a command line syntax error.
28	Command failed because a required file was not found.
36	Command failed because a target disk or directory was not available.
100	Command failed because of an external error.

Recovery Information

The PUT2PROD EXEC can be restarted by issuing the command again.