UPDATE PGM command

Use the UPDATE PGM command to update program resources.

A program resource defines the resource requirements for application programs that run under the control of the DB/TM environment, as well as for application programs that access databases through DBCTL. Program resources combined with transactions define the scheduling and resource requirements for an application program.

Subsections:

Environment

The following table lists the environments (DB/BC, DBCTL, and DCCTL) in which you can use the commands and keywords.

Table 1. Valid environments for the UPDATE PGM command and keywords
Command / Keywords DB/DC DBCTL DCCTL
UPDATE PGM X X X
NAME X X X
OPTION X X X
SET X X X
START X X X
STOP X X X

Syntax

Read syntax diagramSkip visual syntax diagram
                          .-,----.     
                          V      |     
>>-+-UPDATE-+--PGM--NAME(---name-+-)---------------------------->
   '-UPD----'                          

            .-,---------.                             
            V           |                             
>--+-START(---+-SCHD--+-+-)-----------------------+------------->
   |          '-TRACE-'                           |   
   |       .-,---------.                          |   
   |       V           |                          |   
   +-STOP(---+-SCHD--+-+-)------------------------+   
   |         '-TRACE-'                            |   
   |        .-,---------.         .-,---------.   |   
   |        V           |         V           |   |   
   +-START(---+-SCHD--+-+-)-STOP(---+-SCHD--+-+-)-+   
   |          '-TRACE-'             '-TRACE-'     |   
   |      .-,----------------------------.        |   
   |      V                              |        |   
   '-SET(---+-BMPTYPE(-+-Y-+-)---------+-+-)------'   
            |          '-N-'           |              
            +-DOPT(-+-N-+-)------------+              
            |       '-Y-'              |              
            +-FP(-+-E-+-)--------------+              
            |     '-N-'                |              
            +-GPSB(-+-N-+-)------------+              
            |       '-Y-'              |              
            +-LANG(-+-ASSEM--+-)-------+              
            |       +-COBOL--+         |              
            |       +-JAVA---+         |              
            |       +-PASCAL-+         |              
            |       '-PLI----'         |              
            +-LOCK(-+-ON--+-)----------+              
            |       '-OFF-'            |              
            +-RESIDENT(-+-N-+-)--------+              
            |           '-Y-'          |              
            +-SCHDTYPE(-+-PARALLEL-+-)-+              
            |           '-SERIAL---'   |              
            '-TRANSTAT(-+-N-+-)--------'              
                        '-Y-'                         

>--+----------------+------------------------------------------><
   '-OPTION(ALLRSP)-'   

Keywords

The following keywords are valid for the UPDATE PGM command:

NAME
Specifies the 1-8 character name of the program. Wildcards can be specified in the name. The name is a repeatable parameter. If the NAME parameter specified is a specific or wildcard name, command responses are returned for all the resource names that are processed. For NAME(*), command responses are returned only for the resource names that resulted in an error. OPTION(ALLRSP) can be specified with NAME(*) to obtain the command responses for all the resource names that are processed.
OPTION
Specifies functions to be performed along with the command.
ALLRSP
Indicates that the response lines are to be returned for all resources that are processed on the command. The default action is to return response lines only for the resources that resulted in an error. It is only valid with NAME(*). ALLRSP is ignored for other NAME values.
SET
Specifies the attribute values to be changed.
BMPTYPE
BMP type option. Specifies whether the program runs in a BMP type region (Y) or not (N). A BMP type region can be a BMP region or a JBP region. Updating this attribute stops the program from scheduling during command processing.

Start of changeWhen a program is updated to BMPTYPE(Y), the scheduling priority of the transactions that reference the program must be set to zero, and the parallel processing limit must be set to 65535. All transactions that reference the program must be updated to set CPRI, LPRI, and NPRI to 0 and PARLIM to 65535.End of change

Start of changeFor any programs that have been modified from BMPTYPE(N) to BMPTYPE(Y), the following sequence of commands can be issued to locate and update all transactions that reference those programs:
  1. Issue the QUERY PGM NAME(pgmname) SHOW(TRAN) command to find all of the transactions that reference the program.
  2. For each transaction found that references the program, issue the QUERY TRAN NAME(tranname) SHOW(CPRI, NPRI, LPRI, PARLIM) command to determine the current CPRI, NPRI, LPRI, and PARLIM values.
  3. For any transactions that have CPRI, NPRI, or LPRI values that are not set to zero or a PARLIM value that is not 65535, issue an UPDATE TRAN NAME(tranname) SET(CPRI(0),NPRI(0),LPRI(0),PARLIM(65535)) command to correct the values.
End of change

PSBs scheduled by DB2® stored procedures, by programs running under WebSphere® Application Server, and by other users of the ODBA interface might be defined with BMPTYPE Y or N.

Y
The program runs in a BMP type region. It might run in an IMS™ BMP region or a JBP region. Any associated transactions are assigned normal and limit priority values of zero.
N
The program does not run in a BMP type region. It might run in an IMS TM MPP, JMP, or IFP region or it might use either the ODBA or DRA interface. This specification should be used for programs running in IMS TM MPP, JMP, and IFP regions, or PSBs scheduled by CICS® programs using DBCTL and other users of the DRA interface. This is the default.

Keyword combination rules include the following:

  • FP(E) and BMPTYPE(Y) are mutually exclusive.
DOPT
Specifies the dynamic option.
N
The PSB associated with this program is not located dynamically. The PSB must exist in ACBLIB, otherwise the program is set to a NOTINIT status, and cannot be scheduled.
Y
The PSB associated with this program is located dynamically. Each time the program associated with this PSB is scheduled, the latest copy of the PSB is loaded from ACBLIB. The PSB does not need to be in any data set defined for ACBLIB until it is actually required to process a transaction. A new version of the PSB can be genned in ACBLIB and is picked up the next time the PSB is scheduled. DOPT PSBs referencing DBDs that are missing from ACBLIB cannot be scheduled. When the program terminates, the PSB is deleted from the PSB pool.
Updating this attribute stops the program from scheduling for the duration of command processing.

Keyword combination rules include the following:

  • DOPT(Y) and GPSB(Y) are mutually exclusive.
  • DOPT(Y) and LANG(JAVA) is a valid combination.
  • LANG is invalid with GPSB(N), except if DOPT(Y) and LANG(JAVA).
  • LANG(JAVA), DOPT(Y), and GPSB(N) is a valid combination.
  • RESIDENT(Y) and DOPT(Y) are mutually exclusive.
  • SCHDTYPE(PARALLEL) and DOPT(Y) are mutually exclusive.
FP
Specifies the Fast Path option.
E
The program is a Fast Path-exclusive application program. This implicitly defines a wait-for-input (WFI) application program. Either a transaction or a routing code that can be assigned by the user Input Edit/Routing exit routine must be defined for the Fast Path-exclusive application, in order for this program to be usable.
N
The program is not a Fast Path-exclusive application program. When FP(N) is specified, any attempt to use Fast Path resources or commands might yield unpredictable results.

Updating this attribute is rejected if any routing codes or transactions that reference this program have conflicting attributes. To update this attribute, you might need to delete the routing codes and transactions that reference it. Updating this attribute stops the program from scheduling for the duration of command processing.

Keyword combination rules include the following:

  • FP(E) requires Fast Path to be defined.
  • LANG(JAVA) and FP(E) are mutually exclusive.
  • BMPTYPE(Y) and FP(E) are mutually exclusive.
GPSB
Specifies the generated PSB option.
N
The PSB associated with the program is not generated by IMS. The PSB must exist in ACBLIB, otherwise the program is set to a NOTINIT status, and cannot be scheduled.
Y
The PSB associated with the program is generated by IMS. It is not loaded from ACBLIB. The scheduling process of all environments generates a PSB containing an I/O PCB and an alternate modifiable PCB. You do not need to perform the PSBGEN and ACBGEN, thus eliminating I/O to the ACBLIB.

The generated PSB contains an I/O PCB named IOPCBbbb and a modifiable, alternate PCB named TPPCB1bb. With an alternate modifiable PCB, an application can use the CHNG call to change the output destination and send output to a destination other than the input destination.

Updating this attribute stops the program from scheduling for the duration of command processing.

Keyword combination rules include the following:

  • DOPT(Y) and GPSB(Y) are mutually exclusive.
  • DOPT(Y) and LANG(JAVA) is a valid combination.
  • GPSB(Y) requires LANG.
  • LANG is invalid with GPSB(N), except if DOPT(Y) and LANG(JAVA).
  • LANG(JAVA), DOPT(Y), and GPSB(N) is a valid combination.
  • RESIDENT(Y) and GPSB(Y) are mutually exclusive.
LANG
Specifies the language interface of the program for a GPSB, or defines a DOPT(Y) program as using the Java™ language.

In order to define a DOPT program using the Java language, the program must be defined with DOPT(Y) and LANG(JAVA). DOPT PSBs are not loaded at IMS restart; they are loaded every time the program is scheduled. When the program is scheduled for the first time, IMS does not know the language until after the program is scheduled in a region and the PSB is loaded. Unless LANG(JAVA) is defined for the DOPT(Y) program, the program is incorrectly scheduled in a non-Java region.

The LANG parameters and their meanings are identified in the following table.

LANG parameter Meaning
ASSEM Assembly language
COBOL COBOL
JAVA Java
PASCAL Pascal
PLI PL/I

Updating this attribute stops the program from scheduling for the duration of command processing.

Keyword combination rules include the following:

  • LANG is invalid with GPSB(N), except if DOPT(Y) and LANG(JAVA).
  • DOPT(Y) and LANG(JAVA) is a valid combination.
  • LANG(JAVA), DOPT(Y), and GPSB(N) is a valid combination.
  • FP(E) and LANG(JAVA) are mutually exclusive.
LOCK
Specifies that the LOCK status is to be set on or off. SET(LOCK(ON | OFF)) cannot be specified with any other SET attribute. SET(LOCK(ON | OFF)) can be specified with the START or STOP keyword.
ON
Locks the program and prevents it from being scheduled.
OFF
Unlocks the program and allows it to be scheduled.
RESIDENT
Specifies the resident option. The RESIDENT(N) option takes effect immediately. The RESIDENT(Y) option takes effect at the next restart, unless an error is encountered such as no ACB for the PSB for the program, or if the program was updated as RESIDENT(Y) after the checkpoint from which this IMS is performing emergency restart.
N
The PSB associated with the program is not resident in storage. The PSB is loaded at scheduling time.
Y
The PSB associated with the program is made resident in storage at IMS cold start or restart. IMS loads the PSB and initializes it.

A resident PSB is accessed in local storage, which avoids I/O to retrieve the ACB.

Updating this attribute stops the program from scheduling for the duration of command processing.

Keyword combination rules include the following:

  • DOPT(Y) and RESIDENT(Y) are mutually exclusive.
  • GPSB(Y) and RESIDENT(Y) are mutually exclusive.
SCHDTYPE

Specifies whether this application program can be scheduled into more than one message region or batch message region simultaneously.

PARALLEL
The application program can be scheduled in multiple regions simultaneously.
SERIAL
The application program can be scheduled in only one region at a time.

Updating this attribute to SCHDTYPE(SERIAL) is rejected if a transaction that references this program is defined with a parallel limit count other than 65535.

Updating this attribute stops the program from scheduling for the duration of command processing.

Keyword combination rules include the following:

  • DOPT(Y) and SCHDTYPE(PARALLEL) are mutually exclusive.
TRANSTAT
Specifies whether transaction level statistics should be logged. The value specified has meaning only if the program is a JBP or a non-message driven BMP. If Y is specified, transaction level statistics are written to the log in an X'56FA' log record.
N
Transaction level statistics should not be logged.
Y
Transaction level statistics should be logged.

The TRANSTAT keyword on the UPDATE PGM or UPDATE PGMDESC command gives the user the ability to override the system default or the current value of the TRANSTAT parameter. If the TRANSTAT keyword is omitted on the UPDATE PGM command, the current transaction level statistics setting is unchanged for the program.

START
Specifies attributes that are to be started.
SCHD
Starts scheduling of the application program. Or, resets the NOTINIT status if set because of an invalid database or DMB, in case the database or DMB has been created since the scheduling failure. If the database or DMB is still invalid when the program is next scheduled, the program will be marked with a status of NOTINIT again.
TRACE

Starts the tracing of the DL/I portion of Data Communications (DC) for the application program. Each DL/I call to a TPPCB, issued by the user application program, is traced on entry to and exit from the DC call handler DFSDLA30. On entry to DFSDLA30 a type 6701-LA3A record is written, on exit from DFSDLA30 a type 6701-LA3B record is written.

Each record contains the following items if applicable:
  • TPPCB
  • Up to 64 bytes of the I/O area
  • SMB
  • PST

If the batch message program (BMP) being traced is the IBM® IMS Queue Control Facility for z/OS® (5697-E99), a 6701-MRQB record is logged by the IMS Queue Control Facility module DFSQMRQ0. The default program name for the IMS Queue Control Facility BMP is MRQPSB, and can be overridden on the MSGQUEUE system definition macro.

Items logged in the 6701-MRQB record, if applicable, are:
  • TPPCB
  • AIB
  • I/O area
  • PST
  • QTPDST
  • QSAPWKAD
  • QMBA
  • PSTDCA
  • REG14-12
STOP
Specifies attributes that are to be stopped.
SCHD
Stops scheduling of the application program.
TRACE
Stops the tracing of the DL/I portion of Data Communications (DC) for the application program.

Usage notes

Resources exist for the life of the IMS unless they are deleted by using a DELETE command. Resources are recoverable across an IMS warm start or emergency restart. Resources are lost if IMS is cold started, unless cold start imports definitions that were exported while IMS was up.

The UPDATE PGM command can be issued only through the OM API. This command applies to DB/DC, DBCTL and DCCTL systems.

This command is not valid on the XRF alternate, RSR tracker, or FDBR region. The UPDATE PGM command specified with SET() is not valid if online change for MODBLKS is enabled (DFSDFxxx or DFSCGxxx defined with MODBLKS=OLC, or MODBLKS not defined), except for SET(LOCK()) and SET(TRANSTAT()).

This command is recoverable.

The UPDATE commands are not allowed for IMS-defined resources, except with keywords START, STOP, SET(LOCK(ON|OFF)), and SET(TRANSTAT(Y|N)). For the UPDATE PGM command, this means Fast Path utility program DBF#FPU0.

The UPDATE PGM command changes a MODBLKS program to a dynamic program with a definition type of UPDATE, if the BMPTYPE, DOPT, FP, GPSB, LANG, RESIDENT, SCHDTYPE, or TRANSTAT value is changed.

Each program is updated individually, unlike the online change process where either all programs are updated or no programs are updated. Most runtime resource definition values for a program can be updated only if the program is not in use. If the program is in use, the update fails.

You can update the status of a program (LOCK, START, STOP) while the program is in use.

If all the attributes specified by the UPDATE command are already defined for the resource, no update is actually made, no resources are quiesced, no log record is created, and a completion code of zero is returned. This avoids unnecessary processor usage when no action needs to be taken.

The following program attributes cannot be updated if online change for MODBLKS is enabled: BMPTYPE, DOPT, FP, GPSB, LANG, RESIDENT, SCHDTYPE.

Output fields

The following table shows the UPDATE PGM output fields. The columns in the table are as follows:
Short label
Contains the short label generated in the XML output.
Start of changeLong labelEnd of change
Start of changeContains the long label generated in the XML output.End of change
Keyword
Identifies keyword on the command that caused the field to be generated. N/A appears for output fields that are always returned. error appears for output fields that are returned only in case of an error.
Meaning
Provides a brief description of the output field.
Start of change
Table 2. Output fields for the UPDATE PGM command
Short label Long label Keyword Meaning
CC CC N/A Completion code
CCTXT CCText error Completion code text that briefly explains the nonzero completion code.
ERRT ErrorText error Error text with diagnostic information. Error text can be returned for a nonzero completion code and contains information that further explains the completion code.
MBR MbrName N/A IMSplex member that built the output line.
PGM PgmName PGM Program name.
End of change

Return, reason, and completion codes

The following table includes the return and reason codes and a brief explanation of the codes. The return or reason code returned for the command might also indicate an error from a CSL request.

Table 3. Return and reason codes for the UPDATE PGM command
Return code Reason code Meaning
X'00000000' X'00000000' Command completed successfully. The command output contains a line for each resource, accompanied by its completion code. If NAME(*) is specified without OPTION(ALLRSP), no output lines are returned. See the completion code table for details.
X'00000004' X'00002008' Invalid number of keywords. Either a SET, START, or STOP keyword is required.
X'00000008' X'00002040' More than one filter value is specified on the UPDATE PGM command. Confirm that only one of SET or START | STOP filters are specified on the command.
X'00000008' X'00002044' The UPDATE PGM command is not processed because the same attribute value was specified for the START and STOP filters. The attributes SCHD and TRACE can be specified only with the START or STOP keyword, not both. Confirm that only one START | STOP attribute is specified on the command.
X'00000008' X'00002048' Invalid SET attribute.
X'00000008' X'00002106' DOPT(Y) is mutually exclusive with RESIDENT(Y).
X'00000008' X'00002107' DOPT(Y) is mutually exclusive with SCHDTYPE(PARALLEL).
X'00000008' X'0000210B' FP(E) is mutually exclusive with BMPTYPE(Y).
X'00000008' X'0000210D' FP(E) is mutually exclusive with LANG(JAVA).
X'00000008' X'00002113' GPSB(Y) is mutually exclusive with DOPT(Y).
X'00000008' X'00002114' GPSB(N) is mutually exclusive with LANG.
X'00000008' X'00002115' GPSB(Y) is mutually exclusive with RESIDENT(Y).
X'00000008' X'00002132' DOPT(Y) not supported with LANG except for LANG(JAVA).
X'0000000C' X'00003000' Command was successful for some resources but failed for others. The command output contains a line for each resource, accompanied by its completion code. If NAME(*) is specified without OPTION(ALLRSP), only resources with nonzero completion codes are returned. See the completion code table for details.
X'0000000C' X'00003004' Command was not successful for any of the resources. The command output contains a line for each resource, accompanied by its completion code. See the completion code table for details.
X'00000010' X'0000400C' Command is not valid on the XRF alternate.
X'00000010' X'00004014' Command is not valid on the RSR tracker.
X'00000010' X'00004024' No Fast Path defined, FP(E) is invalid.
X'00000010' X'00004120' Online change phase is in progress.
X'00000010' X'00004300' Command is not allowed because online change for MODBLKS is enabled (DFSDFxxx or DFSCGxxx defined with MODBLKS=OLC, or MODBLKS not defined).
X'00000014' X'00005004' DFSOCMD response buffer could not be obtained.
X'00000014' X'00005008' DFSPOOL storage could not be obtained.
X'00000014' X'0000500C' AWE could not be obtained.

Errors unique to the processing of this command are returned as completion codes. The following table includes an explanation of the completion codes.

Table 4. Completion codes for the UPDATE PGM command
Completion code Completion code text Meaning Error text
0   Command completed successfully for program.  
10 NO RESOURCES FOUND Program name is invalid, or the wildcard parameter specified does not match any program names.  
17 ANOTHER CMD IN PROGRESS Another command (such as DELETE or UPDATE) is in progress for this program. This could also mean this command, if the program is specified by more than one specific or wildcard parameter.  
29 Start of changeDOPT=Y/RESIDENT=Y CONFLICTEnd of change Program update failed because dynamic DOPT(Y) option conflicts with resident RESIDENT(Y) option.  
2A Start of changeDOPT=Y/PARALLEL CONFLICTEnd of change Program update failed because dynamic DOPT(Y) option conflicts with parallel schedule SCHDTYPE(PARALLEL) option.  
2F Start of changeFP=E/BMPTYPE=Y CONFLICTEnd of change Program update failed because Fast Path exclusive FP(E) option conflicts with BMP type BMPTYPE(Y).  
36 Start of changeRTC/FP=N PGM CONFLICTEnd of change Program update failed because non-Fast Path option FP(N) conflicts with Fast Path exclusive transaction that references this program.  
37 Start of changeFP=E/LANG=JAVA CONFLICTEnd of change Program update failed because Fast Path exclusive FP(E) option conflicts with Java language LANG(JAVA).  
3E Start of changeFP=N/FP=E PGM CONFLICTEnd of change Program update failed because Fast Path exclusive FP(E) option conflicts with non-Fast Path transaction that references this program. tranname (8 chars)
3F Start of changeFP=P/BMPTYPE=Y CONFLICTEnd of change Program update failed because BMP type program conflicts with Fast Path potential transaction that references this program. tranname (8 chars)
40 Start of changePARLIM/SCHDTYPE=SERIAL CONFLICTEnd of change The SCHDTYPE value cannot be changed to SERIAL because a transaction that references the program has a PARLIM value that is something other than 65535. The program definition is not updated.  
43 Start of changeGPSB=Y/DOPT=Y CONFLICTEnd of change Program updated failed because generated PSB GPSB(Y) option conflicts with dynamic DOPT(Y) option.  
Start of change46End of change Start of changeGPSB=N/LANG CONFLICTEnd of change Start of changeGenerated PSB option N (GPSB(N)) conflicts with the language option (LANG()). The program definition is not updated. End of change Start of change End of change
47 Start of changeGPSB=Y/RESIDENT=Y CONFLICTEnd of change Program update failed because generated PSB GPSB(Y) option conflicts with the resident RESIDENT(Y) option.  
48 NOT ALLOWED FOR IMS RESOURCE The specified UPDATE command is not allowed for the IMS-defined resource. DBF#FPU0 is an example of an IMS-defined program.  
73 PROGRAM SCHEDULED Program is scheduled.  
7A Start of changeRTC/FP=N PGM CONFLICTEnd of change

Program to be updated as FP(N) conflicts with a routing that references the program. The routing code name is returned as error text.

Suggested actions: Issue DELETE RTC command or DELETE TRAN (if associated with FP exclusive transaction) to delete the routing code.

Or

Issue UPDATE RTC command to update the program to another name.

rtcodename (8 chars)
97 Start of changeDOPT=Y/LANG CONFLICTEnd of change Program update failed because dynamic option DOPT(Y) conflicts with LANG specified. DOPT(Y) is only supported with LANG(JAVA).  
99 NOT INITIALIZED Update program failed because the program was not successfully initialized. You can use the QRY PGM SHOW(STATUS) command to return additional information regarding the reason for the NOTINIT status.  
B9 REQUIRES LANG Program update failed because the DOPT(Y) or GPSB(Y) option specified requires language LANG to be specified or already defined.  
BA NOT ALLOWED FOR MRQ PSB UPDATE command failed for MRQ PSB because an attribute was specified that is not supported for the MRQ PSB: BMPTYPE(N), DOPT(Y), GPSB(Y), FP(E), RESIDENT(Y), SCHDTYPE(SERIAL).  
Start of change1D7End of change Start of changeIMPORT CHANGE LIST ERROREnd of change Start of changeThe resource is in the process of being imported from the change list in the IMSRSC repository or was not successfully imported from the change list. The resource cannot be updated until it is successfully imported from the repository.End of change Start of change End of change

Examples

The following are examples of the UPDATE PGM command:

Example 1 for UPDATE PGM command

TSO SPOC input:
UPDATE PGM NAME(BADNAME,AUTPSB2,CDEBS,BMP011,BAD*) SET(SCHDTYPE(PARALLEL))
TSO SPOC output:
Response for: UPDATE PGM NAME(BADNAME,AUTPSB2,CDEBS,BMP011,BAD*) SET(SCHDTYPE(PARALLEL))   
PgmName  MbrName    CC CCText                                        
AUTPSB2  IMS1        0                                               
BAD*     IMS1       10 NO RESOURCES FOUND                            
BADNAME  IMS1       10 NO RESOURCES FOUND                            
BMP011   IMS1       2A Start of changeDOPT=Y/PARALLEL CONFLICTEnd of change                     
CDEBS    IMS1        0  
OM API input:
CMD(UPDATE PGM NAME(BADNAME,AUTPSB2,CDEBS,BMP011,BAD*) SET(SCHDTYPE(PARALLEL)))
OM API output:
<imsout>                                    
<ctl>                                       
<omname>OM1OM   </omname>                   
<omvsn>1.3.0</omvsn>                        
<xmlvsn>20  </xmlvsn>                       
<statime>2006.311 00:55:21.981467</statime> 
<stotime>2006.311 00:55:21.981970</stotime>
<staseq>BFAADF0EA2A1B548</staseq>                          
<stoseq>BFAADF0EA2C12E48</stoseq>                          
<rqsttkn1>USRT011 10165521</rqsttkn1>                      
<rc>0200000C</rc>                                          
<rsn>00003008</rsn>                                        
<rsnmsg>CSLN054I</rsnmsg>                                  
<rsntxt>None of the clients were successful.</rsntxt>      
</ctl>                                                     
<cmderr>                                                   
<mbr name="IMS1    ">                                      
<typ>IMS     </typ>                                        
<styp>DBDC    </styp>                                      
<rc>0000000C</rc>                                          
<rsn>00003000</rsn>                                        
<rsntxt>At least one request successful</rsntxt>           
</mbr>                                                     
</cmderr>                                                  
<cmd>                                                      
<master>IMS1    </master>                                  
<userid>USRT011 </userid>                                  
<verb>UPD </verb>                                          
<kwd>PGM             </kwd>                                
<input>UPDATE PGM NAME(BADNAME,AUTPSB2,CDEBS,BMP011,BAD*)
SET(SCHDTYPE(PARALLEL)) </input>                                      
</cmd>                                                                 
<cmdrsphdr>                                                            
<hdr slbl="PGM" llbl="PgmName" scope="LCL" sort="a" key="1" scroll="no"
 len="8" dtype="CHAR" align="left" />                                  
<hdr slbl="MBR" llbl="MbrName" scope="LCL" sort="a" key="2" scroll="no"
 len="8" dtype="CHAR" align="left" />                                  
<hdr slbl="CC" llbl="CC" scope="LCL" sort="n" key="0" scroll="yes"     
 len="4" dtype="INT" align="right" skipb="no" />                       
<hdr slbl="CCTXT" llbl="CCText" scope="LCL" sort="n" key="0"           
 scroll="yes" len="*" dtype="CHAR" skipb="yes" align="left" />         
<hdr slbl="ERRT" llbl="ErrorText" scope="LCL" sort="n" key="0"         
 scroll="yes" len="*" dtype="CHAR" skipb="yes" align="left" />         
</cmdrsphdr>                                                           
<cmdrspdata>                                                           
<rsp>PGM(BADNAME ) MBR(IMS1) CC(  10) CCTXT(NO RESOURCES FOUND) </rsp> 
<rsp>PGM(AUTPSB2 ) MBR(IMS1) CC(   0) </rsp>                           
<rsp>PGM(CDEBS   ) MBR(IMS1) CC(   0) </rsp>                           
<rsp>PGM(BMP011  ) MBR(IMS1) CC(  2A) Start of changeCCTXT(DOPT=Y/PARALLEL CONFLICT)End of change 
</rsp>                                                                 
<rsp>PGM(BAD*    ) MBR(IMS1) CC(  10) CCTXT(NO RESOURCES FOUND) </rsp> 
</cmdrspdata>                                                        
</imsout>       

Explanation: Update some programs so that they can be scheduled in multiple regions simultaneously. The update completed successfully for programs AUTPSB2 and CDEBS, as shown by the completion code 0. The update failed for program BMP011 with completion code 2A, indicating that the SCHDTYPE(PARALLEL) attribute conflicts with the DOPT(Y) attribute already defined for program BMP011. The update fails for program BADNAME and for parameter BAD* with completion code 10, since program BADNAME does not exist and no program name starts with BAD.