Dynamically modifying the JES3 configuration

The *MODIFY,CONFIG command can be used to add the following initialization statement definitions to JES3 without having to restart JES3:

SNA RJP
- RJPWS - SNA RJP workstation characteristics
- CONSOLE - SNA RJP consoles
- DEVICE - SNA RJP devices
Non-channel attached FSS printers
- FSSDEF - Functional Subsystem Definition
- DEVICE - for non-channel attached FSS printers
Network Job Entry
- DESTDEF - destination definitions

The first thing that must be done is that a member must be created that contains the initialization statements to be added. See z/OS JES3 Initialization and Tuning Guide for more information about creating the member containing the initialization statements and the types of statements that can appear in the member.

The following shows a member NEWRJP which contains the initialization statements needed to add a new SNA RJP workstation and its console to the JES3 configuration.

 Member NEWRJP:

   RJPWS,
      N=TEST1,C=S,PR=3,PU=3
   *
   CONSOLE,
      TYPE=RJP,JNAME=TEST1,LEVEL=15,DEST=ALL,LL=80

To add the new SNA RJP definition to the JES3 configuration, you issue the *MODIFY,CONFIG command:

*MODIFY,CONFIG,ADD=NEWRJP

If your installation's IATUX15 gets control to examine the initialization statements, you may need to specify a parameter string to be passed to the user exit. The parameter string is installation dependent and can be from 1 to 8 characters:

*MODIFY,CONFIG,ADD=NEWRJP,P=xxxxxxxx

During *MODIFY,CONFIG processing, a log data set is created that contains the initialization statements and any messages that are generated. The log data set is spun off after *MODIFY,CONFIG processing is complete. The default is to always generate a log (LOG=YES). However, you can request that:

A log be generated only if an error occurs (LOG=ERR)
A log should not be generated. All error messages should be displayed on the console (LOG=NO).

After the *MODIFY,CONFIG command is issued, the statements from the initialization stream are read and syntax checked. If a severe error occurs, the following message is issued and *MODIFY,CONFIG processing ends:

IAT8344 CONFIGURATION MODIFICATION FAILED - SEVERE ERROR
        OCCURRED

If error or warning messages were generated as a result of syntax checking the statements, then one of the following messages is issued depending on the severity of the error:

IAT8348 WARNING LEVEL MESSAGE(S) ISSUED DURING INITIALIZATION
        STATEMENT PROCESSING

IAT8348 ERROR LEVEL MESSAGE(S) ISSUED DURING INITIALIZATION
        STATEMENT PROCESSING

   Note: These messages will also appear in the *MODIFY,CONFIG
         log.

The following message is then issued to allow you to confirm the *MODIFY,CONFIG request. At this point, the initialization statements have been syntax checked, but the tables that represent the initialization statements have not been created.

If a log data set was requested:

IAT8337 CONFIRM "*F CONFIG" COMMAND (CONTINUE(U), CANCEL, OR LOG)

If a log data set was not requested:

IAT8337 CONFIRM "*F CONFIG" COMMAND (CONTINUE(U) OR CANCEL)

If message IAT8337 is issued with the "LOG" option, it gives you a chance to spin off the *MODIFY,CONFIG log so that you can look at the error messages that were issued before confirming the *MODIFY,CONFIG request. To request that a copy of the *MODIFY,CONFIG log be generated, issue:

R nn,LOG

A copy of the *MODIFY,CONFIG log will be generated and be made available for printing. Message IAT8337 is then issued without the LOG option:

IAT8337 CONFIRM "*F CONFIG" COMMAND (CONTINUE(U) OR CANCEL)

To cancel the *MODIFY,CONFIG request, issue:

R nn,CANCEL

To continue the *MODIFY,CONFIG request, issue:

R nn,CONTINUE

   ...or...

R nn,U

*MODIFY,CONFIG processing then checks for additional errors based on dependencies between the different initialization statements, and creates the tables to represent the information that was added. If a severe error occurs during this stage, the following message is issued and *MODIFY,CONFIG processing ends:

IAT8344 CONFIGURATION MODIFICATION FAILED - SEVERE ERROR OCCURRED

If errors were detected during syntax checking and the operator did not specify "LOG" to message IAT8337, or additional error messages were detected after syntax checking completed, the following message is issued to remind you to examine the *MODIFY,CONFIG log for error messages:

IAT8069 MESSAGES WERE GENERATED - SEE LOG FOR DETAILS

The checkpointed initialization information is updated so that the changes made as a result of a *MODIFY,CONFIG command remain in effect when a hot start is performed. The *MODIFY,CONFIG log is then made available for printing (if a log was requested), and the following message is then issued to summarize what happened during *MODIFY,CONFIG processing:

IAT8350 CONFIGURATION MODIFICATION IS COMPLETE - NO ERRORS
                                                 WARNING MESSAGES
                                                 ERROR MESSAGES

If the JES3 global is hot started, the changes that were made through the *MODIFY,CONFIG command will remain in effect over the hot start. Another *MODIFY,CONFIG command will not be necessary to add the changes back. If you perform a hot start with refresh, a warm start, or a cold start, the changes will be lost.