MODIFY LOAD command

Read syntax diagramSkip visual syntax diagram
Store a load module on the hard disk, and optionally for a 3745, schedule an IPL:

>>-MODIFY-- --procname--,--LOAD--,--ID--=--ncp_name------------->

   .-,--ACTION--=--ADD-.   
>--+-------------------+---------------------------------------->

>--+-----------------------------------------------------------------------+-->
   |                                     .-,--NOTIFY--=--60--------------. |   
   '-,--IPLTIME--=--(--date--,--time--)--+-------------------------------+-'   
                                         '-,--NOTIFY--=--+-------------+-'     
                                                         +-NO----------+       
                                                         '-time_period-'       

>--+---------------------------------+-------------------------><
   '-,--LOADMOD--=--load_module_name-'   

Read syntax diagramSkip visual syntax diagram
Replace a load module on the hard disk, and optionally for a 3745, schedule an IPL:

>>-MODIFY-- --procname--,--LOAD--,--ID--=--ncp_name------------->

>--,--ACTION--=--REPLACE---------------------------------------->

>--+-----------------------------------------------------------------------+-->
   |                                     .-,--NOTIFY--=--60--------------. |   
   '-,--IPLTIME--=--(--date--,--time--)--+-------------------------------+-'   
                                         '-,--NOTIFY--=--+-------------+-'     
                                                         +-NO----------+       
                                                         '-time_period-'       

>--+---------------------------------+-------------------------><
   '-,--LOADMOD--=--load_module_name-'   

Read syntax diagramSkip visual syntax diagram
Purge a load module from the hard disk:

>>-MODIFY-- --procname--,--LOAD--,--ID--=--ncp_name------------->

>--,--ACTION--=--PURGE--+---------------------------------+----><
                        '-,--LOADMOD--=--load_module_name-'   

Read syntax diagramSkip visual syntax diagram
Cancel an ADD or REPLACE operation in progress:

>>-MODIFY-- --procname--,--LOAD--,--ID--=--ncp_name------------->

>--,--ACTION--=--CANCEL--+---------------------------------+---><
                         '-,--LOADMOD--=--load_module_name-'   

Read syntax diagramSkip visual syntax diagram
Schedule or cancel an automatic IPL for an NCP load module in a 3745:

>>-MODIFY-- --procname--,--LOAD--,--ID--=--ncp_name------------->

>--,--ACTION--=--SETTIME---------------------------------------->

                                         .-,--NOTIFY--=--60--------------.     
>--,--IPLTIME--=--+-(--date--,--time--)--+-------------------------------+-+-->
                  |                      '-,--NOTIFY--=--+-------------+-' |   
                  |                                      +-NO----------+   |   
                  |                                      '-time_period-'   |   
                  '-CANCEL-------------------------------------------------'   

>--+---------------------------------+-------------------------><
   '-,--LOADMOD--=--load_module_name-'   

Read syntax diagramSkip visual syntax diagram
Rename a load module on the 3745 hard disk for MOSS:

>>-MODIFY-- --procname--,--LOAD--,--ID--=--ncp_name------------->

>--,--ACTION--=--RENAME--,--LOADMOD--=--load_module_name-------->

>--,--NEWNAME--=--new_load_module_name-------------------------><

Abbreviations

Operand Abbreviation
MODIFY F
ACTION=ADD ACTION=A
ACTION=CANCEL ACTION=C
ACTION=PURGE ACTION=P
ACTION=RENAME ACTION=N
ACTION=REPLACE ACTION=R
ACTION=SETTIME ACTION=S
IPLTIME=CANCEL IPLT=C
IPLTIME=time IPLT=time
LOADMOD :c .LM  
NEWNAME NEWN
NOTIFY=NO NT=NO
NOTIFY=time NT=time

When using an abbreviation in place of an operand, code the abbreviation exactly as shown in the table. For example, when coding the abbreviation for IPLTIME=CANCEL, code only IPLT=C. Do not code IPLTIME=C.

Purpose

The MODIFY LOAD command is used to control NCP load module contents on IBM® 3720 or 3745 Communication Controller hard disks. The actions that can be performed are:
  • Move a load module from the NCP library to the communication controller hard disk.
  • Replace a load module already on the communication controller hard disk.
  • Purge a load module on the communication controller hard disk.
  • Schedule a load module already on the IBM 3745 Communication Controller hard disk for an automatic IPL, or cancel a scheduled IPL.
  • Rename a load module already on the IBM 3745 Communication Controller hard disk.

For additional information about using the timed IPL and automatic reloading functions, see the z/OS Communications Server: SNA Network Implementation Guide.

Use the DISPLAY DISK command to examine the contents of the communication controller hard disk.

Operands

procname
The procedure name for the command. If procname in the START command was specified as startname.ident, where startname is the VTAM® start procedure and ident is the optional identifier, either startname.ident or ident can be specified for procname.

If procname in the START command was startname, startname must be specified for procname.

ACTION
Specifies the action to take on the load module specified by LOADMOD. See Table 1 for additional information about scheduling or canceling IPL, or adding, purging, moving, or replacing a load module.
ACTION=ADD
Requests that the load module specified by LOADMOD be stored on the communication controller's hard disk. The name specified by LOADMOD cannot be the same name as a load module already on the disk. If the load module to be added is already on the controller hard disk, the command is rejected. (If you do not specify LOADMOD, it defaults to the NCP name specified on the ID operand.)
The 3720 disk holds a maximum of two load modules. The IBM 3745 Communication Controller's hard disk holds a maximum of two load modules per CCU. If you request an ADD of a load module and the maximum number of load modules are on the disk, the request will be rejected. You then have two options:
  • Replace one or both of the load modules already on the disk using the ACTION=REPLACE option.
  • Purge one or all of the load modules already on the disk using the ACTION=PURGE option, and then add the module or modules required with the ACTION=ADD option.
Table 1. Relationship between ACTION and IPLTIME operands
  IPLTIME=time IPLTIME=CANCEL IPLTIME not specified
ACTION=ADD

Requests that the load module specified by LOADMOD be placed on the hard disk. If the load module to be added is already on the hard disk or if the load module slots are already full, the request is rejected.

Requests that the load module be scheduled for IPL at the specified time on the IPLTIME operand. This is an incorrect specification. V NET,ACT, LOADFROM=EXT can be used to load the load module into the CCU.
ACTION=REPLACE

Requests that the load module specified by LOADMOD replace a load module of the same name already on the hard disk. If a load module with the name specified is not on the hard disk, VTAM attempts an ADD of the load module. The rules for a successful ADD then apply to the REPLACE option.

Requests that the load module be scheduled for IPL at the specified time on the IPLTIME operand. This is an incorrect specification. V NET,ACT, LOADFROM=EXT can be used to load the load module into the CCU.

If a scheduled IPL is outstanding for the load module to be replaced, the scheduled IPL is canceled.

ACTION=SETTIME

Requests that the load module specified by LOADMOD, existing on the hard disk, be scheduled for an automatic IPL or have a scheduled IPL canceled. The IPLTIME operand is required.

Requests that the load module be scheduled for IPL (or changes a scheduled IPL) at the specified time on the IPLTIME operand. Requests that the scheduled IPL for the load module be canceled. The load module is not purged from the hard disk. This is an incorrect specification.
ACTION=PURGE

Requests that the load module specified by LOADMOD be purged from the hard disk. If no load module with the name specified by LOADMOD is on the hard disk, no action is taken and the request is rejected.

This is an incorrect specification. This is an incorrect specification. If a scheduled IPL is outstanding for the load module to be purged, the scheduled IPL is canceled.
ACTION=REPLACE
Requests that the load module specified by LOADMOD be replaced on the communication controller's hard disk. The name specified by LOADMOD should have the same name as a load module already on the disk, but this is not required. If a load module with the name specified is not on the disk, VTAM attempts an ADD of the load module. The rules for a successful ADD then apply to the REPLACE option.

You should be aware that the REPLACE option affects the automatic reload of a load module if an NCP abends. If the load module being replaced is the one tagged for automatic IPL by use of the DUMPLOAD operand on the VARY ACT command or the DUMPLD operand on the PCCU definition statement (that is, the load module to be reloaded if an NCP abend occurs), it is no longer tagged for automatic IPL after the replace operation begins, nor is the load module retagged for automatic IPL after the replace operation completes.

If the load module being replaced is not the load module tagged for automatic IPL, the automatic IPL tag is not affected during or after the replace of the other load module.

ACTION=PURGE
Requests that the load module and scheduled IPL (if applicable) specified by LOADMOD be purged from the hard disk. Only one load module is purged by this command. Issue a separate PURGE command for each load module to be purged. If no load module with the name specified by LOADMOD is on the disk, no action is taken and an error message is issued.

Before issuing a subsequent MODIFY LOAD command of any type, wait for the completion message of the purge request.

Note: ACTION=PURGE is not valid with the IPLTIME or NOTIFY operands.
ACTION=CANCEL
Requests that a nondisruptive MODIFY LOAD ACTION=ADD or REPLACE option be canceled. The command cannot be disruptive, and must still be executing in order to be canceled. This command does not reverse the process if the process is finished executing. The load module name specified for the CANCEL option must match the load module name specified in the ADD or REPLACE option that is to be canceled.

Regardless of whether the specified load module was originally tagged for automatic IPL, canceling an ADD or REPLACE option results in a PURGE of the partial load module on the disk.

Note: ACTION=CANCEL is not valid with the IPLTIME or NOTIFY operands.

A nondisruptive PURGE cannot be canceled with this command.

ACTION=SETTIME
Requests that the load module specified by LOADMOD, which exists on the IBM 3745 Communication Controller hard disk, either be scheduled for automatic IPL or have its scheduled IPL canceled. If you use SETTIME, the IPLTIME operand is required.

See Table 1 for additional information about scheduling IPL.

You can use the DISPLAY DISK command to display the scheduled IPL time.

ACTION=RENAME
Requests that the load module on the IBM 3745 Communication Controller hard disk be renamed. This command changes the name MOSS associates with a specified load module on the disk. The internal NCP names (specified in the NCP generation definition) are not affected by this command. If you use RENAME, both the LOADMOD and NEWNAME operands are required.

Renaming a load module that already has a timed IPL set does not cancel the scheduled IPL.

ID=ncp_name
Specifies the name of an active NCP (as specified in the PUNAME operand of the BUILD statement during NCP generation) that is on the communication controller whose associated hard disk is to be modified.
IPLTIME
Specifies the scheduled IPL time or cancels an existing scheduled IPL from the hard disk into the CCU. This operand is valid with ACTION=SETTIME, ADD, or REPLACE.

IPLTIME can be specified only when an IBM 3745 Communication Controller is being used.

Each load module can have only one IPL time selected for it. Two load modules on the same CCU cannot have estimated IPL times within 5 minutes of each other.

If the time you specify as the IPL time is the same as the current system time, MOSS does not restart the system. See the VARY ACT command for information about how to cause an immediate IPL.
IPLTIME=(date,time)
Specifies the time of the scheduled IPL. The format of the date entered is determined by the value specified on the DATEFORM start option. The valid possible values for this operand are:
  • DATEFORM=MDY (default); date format is mm/dd/yy. The delimiters can be either slash (/) or dash (–).
  • DATEFORM=DMY; date format is dd/mm/yy. The delimiters can be either slash (/) or period (.).
  • DATEFORM=YMD; date format is yy/mm/dd. The delimiters can be slash (/), period (.), or dash (–).

For example, if DATEFORM=MDY is in effect, specify the IPL time in the form IPLTIME=(mm/dd/yy,hh:mm).

If the year is omitted, the current year is used. The command is rejected if the value entered for the date or time conflicts with any of the following restrictions:
  • Date or time is not valid.
  • Date or time is greater than 90 days from the current date or time. (If you specify a time interval greater than 15 days, minor MOSS clock deviation might occur.)
  • Date or time is before current date or time.
The time hh:mm must be specified in military format (24-hour day) and is time zone independent. See Table 2 for examples of time specifications.
Table 2. Examples of time specifications for IPLTIME
Location of operator Location of 3745 for the scheduled IPL Difference in time zones between the operator and 3745 Time specified in IPLTIME Time of scheduled IPL at 3745
Los Angeles New York + 3 hours 14:00 17:00
Paris London - 1 hour 13:00 12:00
Tokyo Tokyo 0 hours 23:00 23:00
IPLTIME=CANCEL
Indicates that a scheduled IPL for the specified load module be canceled. ACTION=SETTIME is required.
LOADMOD=load_module_name
Specifies the name of the NCP load module. For ACTION=REPLACE or PURGE, the load module on the disk does not have to be the load module currently active in the communication controller.

For ACTION=ADD, ACTION=REPLACE, ACTION=PURGE, or ACTION=SETTIME, the LOADMOD operand, when not coded, defaults to the name specified for the ID operand. For ACTION=CANCEL, LOADMOD defaults to the name of the load module currently being loaded, if a load is in progress.

For ACTION=RENAME, the LOADMOD operand is required.

For ACTION=ADD or ACTION=REPLACE, the load module specified must be one of the load modules in the load library specified by the LOADLIB operand of the BUILD definition statement for the active NCP.

NEWNAME=new_load_module_name
Specifies the new name to be given to the load module specified by the LOADMOD operand. If the new name is the same as the value already specified in LOADMOD, the command is rejected.

NEWNAME can be specified only when an IBM 3745 Communication Controller is being used. NEWNAME is valid and is required when ACTION=RENAME is specified.

NOTIFY
Specifies if and when an alert is to be sent before the expiration of the scheduled IPL. NOTIFY is valid only when a time is specified in the IPLTIME operand. NOTIFY can be specified only when an IBM 3745 Communication Controller is being used.

An IPLTIME cannot be sooner than the NOTIFY time or the command fails. For example, if NOTIFY is allowed to take the default time (60 minutes) an IPLTIME of less than one hour away is not accepted.

Note: The alert is not displayed by VTAM; it is forwarded to the Tivoli® NetView® for z/OS® for z/OS, where it can be displayed using the hardware monitor.
NOTIFY=mmm
Indicates that an alert will be sent mmm minutes before expiration of the scheduled IPL. The default time is 60 minutes. The maximum value is 999 minutes.
NOTIFY=(hh,mm)
Indicates that an alert will be sent at time hh,mm before expiration of the scheduled IPL. The maximum value is 99,99 (99 hours and 99 minutes).
NOTIFY=NO
Indicates that no alert will be sent before the scheduled IPL.