UPDATE DATAGRP command

Use the UPDATE DATAGRP command to allow changes to the status of the members of a data group.

Environment

The following table lists the environments (DB/DC, DBCTL, and DCCTL) from which the UPDATE DATAGRP command and keywords can be issued.

Command / Keywords DB/DC DBCTL DCCTL
UPDATE DATAGRP X X  
NAME X X  
OPTION X X  
SCOPE X X  
START X X  
STOP X X  

Syntax

Read syntax diagramSkip visual syntax diagram
>>-+-UPDATE-+--DATAGRP--NAME(datagrpname)----------------------->
   '-UPD----'                               

>--+-START-+-(ACCESS)--+--------------------------+-+-+--------->
   |       |           '-SET(ACCTYPE(-+-BRWS-+-))-' | |   
   |       |                          +-EXCL-+      | |   
   |       |                          +-READ-+      | |   
   |       |                          '-UPD--'      | |   
   |       '-(QUIESCE)--+-------------------+-------' |   
   |                    '-SET(TIMEOUT(nnn))-'         |   
   '-STOP(-+-ACCESS--+-)------------------------------'   
           +-QUIESCE-+                                    
           '-SCHD----'                                    

                                    .-SCOPE(ALL)----.   
>--+-----------------------------+--+---------------+----------><
   |         .-,-------------.   |  '-SCOPE(ACTIVE)-'   
   |         V               |   |                      
   '-OPTION(---+-ALLRSP----+-+-)-'                      
               +-DBALLOC---+                            
               +-FEOV------+                            
               +-HOLD------+                            
               +-NODBALLOC-+                            
               +-NOFEOV----+                            
               +-NOHOLD----+                            
               '-PFA-------'                            

Keywords

The following keywords are valid for the UPDATE DATAGRP command:

NAME()
Specifies the name of the data group to be processed.
OPTION()
Specifies the additional functions to be performed. Following is a list of additional functions:
ALLRSP
Indicates that the response lines are to be returned for all the members of the data group (all databases, areas, or both) that are processed on the command.

The default action is to return response lines only for the databases and areas or both that resulted in an error. A response line with the data group name is always returned.

DBALLOC
Indicates that the databases in the data group are to be allocated when they are started.

DBALLOC can only be specified with START(ACCESS).

Only one of DBALLOC or NODBALLOC can be specified.

FEOV
Indicates to force end of volume after the command processing is complete. The IMS™ log switches to the next OLDS, and a simple checkpoint is taken unless specified with STOP(QUIESCE). This switch is marked as a recovery point for log archiving purposes. A simple checkpoint is not taken when specified with STOP(QUIESCE).

FEOV is valid only with START(QUIESCE) OPTION(NOHOLD) or STOP(ACCESS) or STOP(QUIESCE).

FEOV is not valid on an RSR tracker.

OPTION(FEOV) is the default when specified with START(QUIESCE) OPTION(NOHOLD) or STOP(QUIESCE).

For quiesce processing, the end of volume will be forced after the quiesce point has been reached, causing the logs to be switched before the quiesce is released, so that any new updates occur on the new IMS log. This occurs during the stop quiesce processing of a START(QUIESCE) OPTION(NOHOLD) or when a STOP(QUIESCE) is issued to release a quiesce from a previous START(QUIESCE) OPTION(HOLD).

HOLD
Specifies that after the quiesce has been achieved successfully the data group members should remain quiesced. A subsequent STOP(QUIESCE) would be required to release the quiesce on the data group members. This keyword is only valid with the START(QUIESCE) keyword. HOLD is mutually exclusive with NOHOLD.
NODBALLOC
Indicates that the databases in the data group are not to be allocated when they are started. The databases will be allocated when they are scheduled.

NODBALLOC can only be specified with START(ACCESS). NODBALLOC is the default action for UPDATE DATAGRP command if OPTION(DBALLOC) is not specified.

Only one of DBALLOC or NODBALLOC can be specified.

NOFEOV
Indicates to not force end of volume after the command processing is complete. The IMS log does not switch to the next OLDS, and a simple checkpoint is not taken.

NOFEOV is valid only with START(QUIESCE) OPTION(NOHOLD), STOP(ACCESS), or STOP(QUIESCE). OPTION(NOFEOV) is the default when specified with STOP(ACCESS).

NOHOLD
Specifies that after the quiesce has been achieved successfully the data group members should automatically release the quiesce. If you do not specify either HOLD or NOHOLD, NOHOLD is assumed. This keyword is only valid with the START(QUIESCE) keyword. NOHOLD is mutually exclusive with HOLD.
SCOPE()
Specifies where IMS should apply the change.
ACTIVE
SCOPE(ACTIVE) specifies that the changes are to be applied to the IMS systems that are currently active and to which the command is routed.

This option does not apply to the quiesce function. The scope of a quiesce is always all instances of the data group usage across the IMSplex. There is no quiesce which would only apply to a subset of the IMSplex.

ALL
SCOPE(ALL) specifies that the changes are to be applied to the active IMS systems.

This option does not apply to the quiesce function. The scope of a quiesce is always all instances of the data group members usage across the IMSplex. There is not a global status of QUIESCE for a data group or its members. Using SCOPE(ALL) for a START(QUIESCE) or STOP(QUIESCE) does not change the global status for the data group members.

Currently, ACTIVE and ALL produce the same results.

SET()
Specifies the attribute values to be changed or sets the database state.
ACCTYPE
Specifies the access intent for the named database. This keyword can be specified only if START(ACCESS) is specified. This keyword overrides the database access intent specified at system definition.
BRWS
Specifies that the named database is available for read-only processing on this IMS subsystem. The only programs that can use the database on this subsystem are those that have a PCB processing option of GO (PROCOPT=GO). Programs that access the data using the GO processing option might see uncommitted data because another program could be updating the database. The database is opened for read-only processing.
EXCL
Specifies that the named database is to be used exclusively by this IMS subsystem. This exclusive access is guaranteed only when the database is registered to DBRC.
READ
Specifies that the named database is available for read-only processing in this IMS subsystem. Programs with update intent can be scheduled, but cannot update the database. ACCTYPE of READ differs from ACCTYPE of BRWS in that the data is read with integrity (locking is performed) and all programs can access the data, not just those with a processing option of GO. The database is opened for read-only processing.
UPD
Specifies that the named database is available for update as well as read processing in this IMS subsystem.
TIMEOUT(nnn)
Specifies the number of seconds to wait before a timeout occurs in a data group quiesce. The timeout value can be 1 - 999 seconds. The TIMEOUT parameter value can override the DBQUIESCETO parameter in the DFSCGxxx member of the IMS PROCLIB data set. If the TIMEOUT parameter is omitted and the DBQUIESCETO parameter is not specified, the default timeout value is 30 seconds. The TIMEOUT keyword is valid only with the START(QUIESCE) keyword.
START()
Specifies the attributes that are to be started.
ACCESS
Specifies that the members of the specified data group name are to be started. See UPDATE AREA START(ACCESS) and UPDATE DB START(ACCESS) for a description of the actions performed on the databases and areas in the data group.

Additional functions to be performed along with START(ACCESS) can be specified using the OPTION keyword.

An UPDATE DATAGRP START(ACCESS) command with SET(ACCTYPE) or OPTION(DBALLOC | NODBALLOC | NOBACKOUT | OPEN | NOOPEN) is invalid on the RSR tracker.

QUIESCE
Specifies that the data group named on the command is to be quiesced to establish a new recovery point. The scope of a quiesce is always all instances of the data group usage across the IMSplex.
STOP()
Specifies the attributes to be stopped.
ACCESS
Specifies that offline processing is to be done for the members of the specified data group. See UPDATE AREA STOP(ACCESS) and UPDATE DB STOP(ACCESS) for a description of the actions performed on the databases and areas in the data group.
QUIESCE
Specifies that the data group named on the command should be made available again by releasing the quiesce on the data group members.

Unlike START(QUIESCE), where each data group resource listed must be quiesced in order for the command to complete successfully, STOP(QUIESCE) continues to process each listed resource even if some resources are not in quiesced state or cannot be released from quiesced state. For those resources that are not in quiesced state or cannot be released from quiesced state, the command returns a response line for each of those resources.

SCHD
Specifies that the members of the specified data group name are to be stopped. See UPDATE AREA STOP(ACCESS) and UPDATE DB STOP(ACCESS) for a description of the actions performed on the databases and areas in the data group.

Usage notes

The UPDATE DATAGRP command can only be specified through the OM API and can be processed only by the DB/DC and DBCTL environments. In addition, the UPDATE DATAGRP command is not allowed on the XRF alternate.

When the UPDATE DATAGRP command is issued, it only applies to the IMS system to which it is routed. It does not apply to the other IMS systems in the IMSplex that share the database or areas in the data group. The routing of the UPDATE DATAGRP command is done by OM. OM routes the command to all active DB/DC or DBCTL IMS systems, unless specific routing is specified. OM selects one IMS as the command master.

A response line is returned for the data group name from each IMS. Response lines are also returned for each data group member that resulted in an error. No response lines are returned for the data group members that are processed successfully unless OPTION(ALLRSP) is specified.

A data group is defined in the RECON data set by using the INIT.DBDSGRP command with the parameters GRPNAME and DBGRP (to define a DB group), MEMBERS (to define a DBDS group), or RECOVGRP (to define a recovery group). The DATAGRP keyword on the UPDATE command can specify either a DBDS group or a DB group (DL/I databases or DEDB areas).

If the ACCESS keyword is specified on the UPDATE DATAGRP command along with the DBDS group name, the ACCESS keyword is not applied to the Fast Path DEDB databases associated with the Fast Path DEDB areas in the DBDS group. If the intent is to use the ACCESS keyword for Fast Path DEDB databases, the DATAGRP parameter must be a data group name that does not contain area names.

While the database is being quiesced, this command with keywords other than STOP(QUIESCE) cannot be processed successfully.

Equivalent IMS type-1 commands

The following table shows variations of the UPDATE DATAGRP command and the type-1 IMS commands that perform similar functions.

Table 1. Type-1 equivalents for the UPDATE DATAGRP command
UPDATE DATAGRP command Similar IMS type-1 command
UPDATE DATAGRP NAME(name) STOP(ACCESS) /DBR DATAGRP datagrpname
UPDATE DATAGRP NAME(name) START(ACCESS) /START DATAGRP datagrpname
UPDATE DATAGRP NAME(name) STOP(SCHD) /STOP DATAGRP datagrpname

Output fields

The following table shows the output fields for the UPDATE DATAGRP. The columns in the table are as follows:
Short label
Contains the short label generated in the XML output.
Keyword
Identifies the keyword on the command that caused the field to be generated. N/A appears for output fields that are always returned. ERR appears for output fields that are returned only in case of an error.
Meaning
Provides a brief description of the output field.
Table 2. Output fields for UPDATE DATAGRP command
Short label Keyword Meaning
AREA N/A Area name. The Area name is returned if there are one or more areas in the data group.
CC N/A Completion code for the line of output. Completion code is always returned.
CCTXT error The completion code text that briefly explains the meaning of the completion code.
DB N/A Database name. The database name is returned if there are one or more databases in the data group.
DG N/A Data group name. The data group name is always returned.
ERRT ERR Error text returned to add more meaning to the completion code and may include a return code from a service. The error text is only returned if the completion code is non-zero.
MBR N/A The IMSplex member that built output line. The IMS identifier of the IMS for which the database information is displayed. The IMS identifier is always returned.

Return, reason, and completion codes

An IMS return and reason code is returned to OM by the UPDATE DATAGRP command. The OM return and reason codes that may be returned as a result of the UPDATE DATAGRP command are standard for all commands entered through the OM API.

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 DATAGRP command
Return code Reason code Meaning
X'00000000' X'00000000' The UPDATE DATAGRP command completed successfully.
X'00000008' X'00002004' An invalid keyword or more than one keyword is specified on the UPDATE DATAGRP command.
X'00000008' X'00002014' The UPDATE DATAGRP command is not processed because an invalid character is found in the data group name.
X'00000008' X'00002040' More than one filter or keyword value is specified on the UPDATE DATAGRP command. Either more than one keyword or an invalid combination of filters was specified. For example, START(ACCESS) and STOP(ACCESS) was specified, or OPTION(DBALLOC,NODBALLOC) was specified. Check the input command and reenter the correct combinations.
X'00000008' X'00005000' The UPD DATAGRP command processing terminated because IMODULE GETSTOR storage could not be obtained.
X'00000008' X'0000501C' The UPD DATAGRP command processing terminated because IMODULE GETMAIN storage could not be obtained.
X'0000000C' X'00003000' The UPDATE DATAGRP command is successful for at least one member in the data group. The UPDATE DATAGRP command is not successful for one or more members in the data group. The completion code indicates the reason for the error with the data group member name. The completion codes that can be returned by the UPDATE DATAGRP command are listed in the UPDATE DATAGRP completion code table.
X'0000000C' X'00003004' The UPDATE DATAGRP command is not successful for all the members in the data group. The completion code indicates the reason for the error with the data group member name. The completion codes that can be returned by the UPDATE DATAGRP command are listed in the UPDATE DATAGRP completion code table.
X'00000010' X'0000400C' The UPDATE DATAGRP command is not processed because it is not valid on the XRF alternate.
X'00000010' X'00004014' The UPDATE DATAGRP command is not processed because it is not valid on the RSR tracker.
X'00000010' X'00004200' Commands are not processed because IMS shutdown is in progress.
Start of changeX'00000010'End of change Start of changeX'00004208'End of change Start of changeInvalid command for RMENV=NO.End of change
X'00000010' X'00004400' MINVERS in the RECON data sets is not 11.1.
X'00000014' X'00005004' The UPDATE DATAGRP command processing terminated because a DFSOCMD response buffer could not be obtained.
X'00000014' X'00005008' The UPDATE DATAGRP command processing terminated because DFSPOOL storage could not be obtained.
X'00000014' X'0000500C' The UPDATE DATAGRP command processing terminated because AWE could not be obtained.
X'00000014' X'00005014' The UPDATE DATAGRP command processing terminated because BCB storage could not be obtained.
X'00000014' X'00005FFF' The UPDATE DATAGRP command processing terminated because of an internal error.
X'02000008' X'0000203C' An invalid TIMEOUT value is specified. The value must be a numeric value between 1 and 999.

The following table includes an explanation of the completion codes. Errors unique to the processing of UPDATE DATAGRP command are returned as completion codes. A completion code is returned for each action against an individual resource.

Table 4. Completion codes for the UPDATE DATAGRP command
Completion code Completion code text Meaning
0   The command completed successfully for the resource.
8 COMMAND COMPLETE FOR SOME Some. The command completed with error for some of the AREAS of the DEDB. Response lines for the area names in error are returned.
C COMMAND COMPLETE FOR NONE None. The command completed with error for all the AREAs of the DEDB. Response lines for the area names in error are returned.
10 NO RESOURCES FOUND No resource found. Database name is invalid, or the wildcard parameter specified does not match any database names.
11 DUPLICATE RESOURCE NAME Duplicate resource name.

The resource name is specified multiple times on the command and is ignored.

17 ANOTHER CMD IN PROGRESS This error is returned when the quiesce could not be started because another database command was in progress.
23 DB STOP ACCESS IN PROGRESS A /DBRECOVERY, or UPDATE DB STOP(ACCESS) command to stop database access is in progress. This takes the database offline.
25 DB STOP UPDATES IN PROGRESS A /DBDUMP or UPDATE DB STOP(UPDATES) command to stop database updates is in progress.
26 DEDB STOP IN PROGRESS /DBRECOVERY, /STOP, or UPDATE DB STOP(SCHD) command to stop database scheduling is in progress for a DEDB.
31 NOT ALLOWED FOR A DEDB Database is a DEDB. The command entered is not valid for the DEDB in the IMS environment.
32 NOT ALLOWED FOR AN MSDB Database is a MSDB. The command entered is not valid for the MSDB in the IMS environment.
33 NOT ALLOWED FOR A HALDB MASTER Command invalid HALDB master. The command OPTION is invalid for the HALDB master but partition structure rebuild will be done if structure rebuild is needed and if only one HALDB master was specified in the command. No rebuild will be attempted if there is more than one database name listed in the command.

If there are multiple database names listed in the command and all are invalid except the HALDB master, then rebuild will be attempted if needed.

48 NOT ALLOWED FOR IMS RESOURCE The specified UPDATE command is not allowed for an IMS descriptor or resource. DFSDSDB1 is an example of an IMS descriptor. The only IMS descriptor attribute you can update is DEFAULT(Y).
53 NO RM ADDRESS SPACE This error is returned when the quiesce could not be started because the RM address space is not present.
55 NO FAST PATH INSTALLED The command failed because Fast Path is not installed.
56 FF DB + LSO=Y + TRK = ERROR Command is invalid on the RSR tracker because of the LSO=Y option.
65 DMB POOL STORAGE ERROR DMB pool storage error. The command failed because of DMB pool storage request failure.
66 DMB POOL FULL DMB pool full. The command failed because the DMB pool was full.
6C NOT ALLOWED FOR A HALDB PARTITION An UPDATE command specified a change to the residency option for a HALDB partition. The residency option is valid only for the master and not the partitions.
6F REFERENCED BY PROGRAM An UPDATE DB command is issued to change the resident option. There is a currently scheduled program that is referencing that database. The UPD command fails.
76 RECOVER CMD ACTIVE /RECOVER START command is in progress to recover one or more databases with the database recovery services.
81 DBRC ERROR DBRC error.
90 INTERNAL ERROR The command entered is not processed because of an internal error.
91 TIMEOUT ERROR This error is returned when the quiesce could not be completed within the timeout period.
92 COMMAND PROCESSING ERROR Command processing error. The command entered is not processed because of a command error. A unique completion code could not be generated to explain the error. The message number and the return code that could not be converted to a completion code are listed in the error text.
A0 DYNAMIC ALLOCATION FAILED Dynamic allocation failed. The command entered is not processed because the dynamic allocation failed for the DB.
A1 DB IS AUTHORIZED BY BATCH Database is authorized by Batch. The command entered is not processed because the database is authorized by batch.
A2 DB IS AUTHORIZED BY ANOTHER IMS Database is authorized by another IMS. The command entered is not processed because the database is authorized by another active or abnormally terminated IMS and its authorization state is incompatible with the current authorization request.
A3 AUTHORIZATION CHANGE FAILED Authorization change failed. The DBRC CHNGAUTH request resulted in an error.
A4 DATABASE NOT REGISTERED TO DBRC Database not registered to DBRC. The command processing failed as the database is not registered to DBRC.
A5 PREVENT FURTHER AUTH ON Prevent Further Auth ON. The command entered is not processed because the database or area is defined to DBRC as prevent further Auth.
A6 INVALID DATABASE RECORD IN RECON Invalid database record in RECON. The command entered is not processed because an invalid parameter was found during the evaluation process of the database usage compatibility. The database record might be invalid in the RECON data set.
A7 DBRC UNAUTH FAILED FOR CHNGAUTH DBRC unauth failed during change authorization. The command is not processed because of an error during UNAUTH processing during change authorization request.
A8 INVALID DB RECORD IN RECON Invalid database record in RECON. An UPDATE DB SET(ACCTYPE) command is entered to change the database authorization level. An encoded state of zero is returned by DBRC during the change authorization processing.
A9 DB OR AREA AUTHORIZATION ERROR Database or area authorization error. For a database, the command entered is not processed because of a database authorization error. For an area, area authorization to DBRC failed.
AA DB IN USE-BMP The UPDATE DB command is rejected because the database is in use by a BMP.
AB DB IN USE-DBCTL LONG THREAD The UPDATE DB command is rejected because the database is in use by a long-running DBCTL thread.
AC FP AREA HELD-LONG BUSY WAIT The UPDATE DB command is rejected because the area of the DEDB is in long-busy wait.
AD DYNAMIC UNALLOCATION FAILED The UPDATE DB command is not successful because of a dynamic unallocation error.
AE DYNAMIC ALLOCATION ERROR The UPDATE DB command is not successful because of a dynamic allocation error. No SVC99 is issued.
C1 OLR DDIR MISSING OR DFSPNT ZERO Unknown DMB referenced for database. The command cannot be processed because an unknown data management block is referenced for the database. Refer to the DFS564I message put out to the system console to identify the DMB name that cannot be referenced.
CC OLR IS ACTIVE FOR DATABASE OLR is active for database. The command failed as OLR is active for the database.
D0 DATABASE CLOSE ERROR Database close error. The command processing failed because of a database close error.
D1 DATABASE WRITE ERROR Database write error. The command processing failed because of a database write error.
D2 DATABASE NEEDS BACKOUT Database needs backout. The command processing failed as the database needs backout.
D3 DATABASE OR AREA NEEDS RECOVERY Database or AREA needs recovery. The command processing failed as the database or area needs recovery.
D4 DATABASE NEEDS IMAGE COPY Database needs image copy. The command processing failed as the database needs image copy.
D5 DATABASE HAS NO BACKOUTS Database has no backouts. The command processing failed as there are no backouts for the database.
D6 DATABASE IN USE Database in use. A SET(ACCTYPE) is specified for the DEDB and the authorization level cannot be changed as the DEDB is in use in a region.
D7 DB I/O PREVENTION NOT COMPLETE Database I/O prevention not complete. The database cannot be started as it is extended because of a XRF takeover and the I/O prevention is not complete.
D8 DATABASE BACKOUTS PENDING Database backouts pending. The access type specified for the database cannot be changed as restartable backouts are pending for the database.
D9 DATABASE/AREA OPEN FAILED Database or area open failed. The command failed because an error occurred while opening the database or area.
DA DATABASE BEING RECALLED BY HSM Database being recalled from HSM. The command processing failed because the database is being recalled from HSM.
DB PARTITION OPEN FAILED Partition open failed. The partition open failed because the master is offline. This can also occur if the partition has been deleted and partition structure rebuild has occurred. Partition structure rebuild can be accomplished by issuing an UPD DB NAME(haldbmst) START(ACCESS) OPTION(OPEN) command, where haldbmst is the partition's master, or by issuing a qualified GU call for a key in the key range of the partition. List.recon can be used to determine if the partition exists or has been deleted.
DC HALDB PARTITION BUILD FAILURE Database partition build failure. The database partition build for the DDIR or DMB failed. Refer to the DFS0415I message sent to the system console to determine the reason of the failure.
DD HALDB PARTITION INIT FAILURE Database partition initialization failed. The database partition initialization for the DDIR or DMB failed. Refer to the DFS0415 message sent to the system console for the details.
DE ACBLIB READ FAILURE ACBLIB read failure. The command is not processed because there was an error reading the ACBLIB.
DF DB DIRECTORY INIT FAILURE Database directory initialization failed. The command is not processed because of a database directory initialization failure.
E0 DATABASE OR AREA IN RECOVERY Database or area in recovery. The command is not processed because the database or area is in recovery.
E1 DATABASE HAS NOT BEEN DBR'ED An UPDATE command changing the residency option of a database was not issued for a database that has not been DBR'ed.
E2 PARALLEL DB OPEN NOT COMPLETE Restart parallel DB open not complete. The command is not processed because the restart parallel DB open is not complete for the database.
E5 PARTICIPANT UNABLE TO QUIESCE This error is returned when the quiesce could not be completed successfully across the IMSplex. The IMS with this completion code was the quiesce participant which was not able to be quiesced.
E6 QUIESCE COMMUNICATION FAILURE This error is returned when the quiesce could not be completed because of a failure to communicate across the IMSplex. There could be a problem with RM, OM, or SCI that has caused the communication failure to occur.
E7 CMD NOT ALLOWED This error is returned when the database command could not be processed because a quiesce command was in progress.
E8 DATABASE HAS INTENT TO REORGANIZE This error is returned when the quiesce could not be started because the RECON data sets indicates that there is intent to reorganize the database.
E9 DB IN WRONG STATE TO BE QUIESCED This error is returned when the named resource is in the wrong state for quiesce processing to proceed.
EE DATABASE BACKOUT ERROR Database backout error. The command processing failed because of a database backout error.
EF DATABASE IS IN ERROR Database is in error. The command entered is not processed because the database is in error.
F0 NO AREA LOCK No AREA lock. The command processing failed because the area lock could not be obtained.
F1 AREA NOT STOPPED Area not stopped. The command entered is not processed because the AREA is not stopped.
F2 PRELOAD IS ACTIVE FOR AREA Preload is active for AREA. The command is not processed because preload is active for the AREA.
F3 UNRESOLVED INDOUBTS FOR AREA Unresolved indoubts for AREA. The command entered is not processed because unresolved indoubts exist for the AREA.
F4 ALLOCATION FAILED Allocation failed. Allocation failed for the AREA name.
F5 AREA NEEDS RECOVERY AREA needs recovery. The command processing failed because the area needs recovery.
F6 ADS NUMBER DISCREPANCY ADS number discrepancy. The command failed for the AREA because there is a discrepancy between the number of ADS allocated by IMS and the number of ADS known to DBRC. Correct the discrepancy and reissue the command to deallocate the data sets.
F7 AREA IS NOT LOADED INTO CF Area is not loaded into CF. The AREA OPEN failed and is not loaded into the Coupling Facility.
F8 AREA HAS I/O TOLERATED CI Area has I/O tolerated CI.

The command is not processed because the AREA has an I/O tolerated CI.

F9 AREA HAS 2ND CI EEQE Area has second CI EEQE.

The command is not processed because the AREA has a second CI EEQE.

FC UTILITY ACTIVE ON AREA This error is returned when the area is in use by a utility.
FD AREA HAS EEQE This error is returned when the area has an extended error queue element (EEQE).
FE AREA HAS EQE This error is returned when the area has an error queue element (EQE).

Examples

The following are examples of the UPDATE DATAGRP command:

Example 1 for UPDATE DATAGRP command

TSO SPOC input:
UPD DATAGRP NAME(GROUP1) STOP(ACCESS)
TSO SPOC output:
DataGroup DBName   AreaName MbrName    CC
GROUP1                      IMSA        0
GROUP1                      IMS1        8 
GROUP1    DEDBJN03          IMS1        C
GROUP1    DEDBJN03 DB3AREA0 IMS1       F0
OM API input:
CMD(UPD DATAGRP NAME(GROUP1) STOP(ACCESS))
OM API output:
<imsout>
<ctl>
<omname>OM1OM   </omname>
<omvsn>1.2.0</omvsn>
<xmlvsn>1   </xmlvsn>
<statime>2003.129 22:45:55.898843</statime>
<stotime>2003.129 22:45:55.990001</stotime>
<staseq>B965346AB45DB229</staseq>
<stoseq>B965346ACA9F1263</stoseq>
<rqsttkn1>USRT005 10154555</rqsttkn1>
<rc>0200000C</rc>
<rsn>00003000</rsn>

</ctl>
<cmderr>
<mbr name="IMS1    ">
<typ>IMS     </typ>
<styp>DBDC    </styp>
<rc>0000000C</rc>
<rsn>00003000</rsn>
<rsntext>At least one request successful</rsntext>
</mbr>
</cmderr>
<cmd>
<master>IMSA    </master>
<userid>USRT005 </userid>
<verb>UPD </verb>
<kwd>DATAGRP         </kwd>
<input>UPD DATAGRP NAME(GROUP1) STOP(ACCESS) </input>
</cmd>
<cmdrsphdr>
<hdr slbl="DG" llbl="DataGroup" scope="LCL" sort="a" key="1"
 scroll="no" len="8" dtype="CHAR" align="left" skipb="no" />
<hdr slbl="DB" llbl="DBName" scope="LCL" sort="a" key="3" scroll="no" 
 len="8" dtype="CHAR" align="left" skipb="yes" />
<hdr slbl="AREA" llbl="AreaName" scope="LCL" sort="a" key="4"
 scroll="no" len="8" dtype="CHAR" align="left" skipb="yes" />
<hdr slbl="MBR" llbl="MbrName" scope="LCL" sort="a" key="2" scroll="no" 
 len="8" dtype="CHAR" align="left" skipb="no" />
<hdr slbl="CC" llbl="CC" scope="LCL" sort="n" key="0" scroll="yes"
 len="4" dtype="INT" align="right" skipb="no" />
<hdr slbl="ERRT" llbl="ErrorText" scope="LCL" sort="n" key="0"
 scroll="yes" len="16" dtype="CHAR" align="left" skipb="yes" />
</cmdrsphdr>
<cmdrspdata>
<rsp>DG(GROUP1  ) MBR(IMSA    ) CC(   0) </rsp>
<rsp>DB(DEDBJN03) AREA(DB3AREA0) DG(GROUP1  ) MBR(IMS1    ) CC(  F0)
</rsp>
<rsp>DB(DEDBJN03) DG(GROUP1  ) MBR(IMS1    ) CC(   C) </rsp>
<rsp>DG(GROUP1  ) MBR(IMS1    ) CC(   8) </rsp>
</cmdrspdata>
</imsout>

Explanation: The command stops access to all the members of data group GROUP1 and takes them offline. The command response lines are returned for all the databases or areas that resulted in an error. No response lines are returned for members for which the command was successful.

Example 2 for UPDATE DATAGRP command

TSO SPOC input:
UPD DATAGRP NAME(GROUP1) START(ACCESS) OPTION(ALLRSP)
TSO SPOC output:
DataGroup DBName   AreaName MbrName    CC
GROUP1                      IMSA        0
GROUP1             DB21AR1  IMSA        0
GROUP1    BE3PARTS          IMSA        0
GROUP1    DEDBJN03          IMSA        0
GROUP1                      IMS1        0
GROUP1             DB21AR1  IMS1        0
GROUP1    BE3PARTS          IMS1        0
GROUP1    DEDBJN03          IMS1        0 
OM API input:
CMD(UPD DATAGRP NAME(GROUP1) START(ACCESS) OPTION(ALLRSP))
OM API output:
<imsout>
<ctl>
<omname>OM1OM   </omname>
<omvsn>1.2.0</omvsn>
<xmlvsn>1   </xmlvsn>
<statime>2003.129 22:46:51.490484</statime>
<stotime>2003.129 22:46:51.672332</stotime>
<staseq>B965349FB88B4445</staseq>
<stoseq>B965349FE4F0C36A</stoseq>
<rqsttkn1>USRT005 10154651</rqsttkn1>
<rc>00000000</rc>
<rsn>00000000</rsn>
</ctl>
<cmd>
<master>IMSA    </master>
<userid>USRT005 </userid>
<verb>UPD </verb>
<kwd>DATAGRP         </kwd>
<input>UPD DATAGRP NAME(GROUP1) START(ACCESS) OPTION(ALLRSP) </input>
</cmd>
<cmdrsphdr>
<hdr slbl="DG" llbl="DataGroup" scope="LCL" sort="a" key="1"
 scroll="no" len="8" dtype="CHAR" align="left" skipb="no" />
<hdr slbl="DB" llbl="DBName" scope="LCL" sort="a" key="3" scroll="no"
 len="8" dtype="CHAR" align="left" skipb="yes" />
<hdr slbl="AREA" llbl="AreaName" scope="LCL" sort="a" key="4" 
 scroll="no" len="8" dtype="CHAR" align="left" skipb="yes" />
<hdr slbl="MBR" llbl="MbrName" scope="LCL" sort="a" key="2" scroll="no"
 len="8" dtype="CHAR" align="left" skipb="no" />
<hdr slbl="CC" llbl="CC" scope="LCL" sort="n" key="0" scroll="yes"
 len="4" dtype="INT" align="right" skipb="no" />
<hdr slbl="ERRT" llbl="ErrorText" scope="LCL" sort="n" key="0"
 scroll="yes" len="16" dtype="CHAR" align="left" skipb="yes" />
</cmdrsphdr>
<cmdrspdata>
<rsp>DB(DEDBJN03) DG(GROUP1  ) MBR(IMSA    ) CC(   0) </rsp>
<rsp>DB(BE3PARTS) DG(GROUP1  ) MBR(IMSA    ) CC(   0) </rsp>
<rsp>AREA(DB21AR1 ) DG(GROUP1  ) MBR(IMSA    ) CC(   0) </rsp>
<rsp>DG(GROUP1  ) MBR(IMSA    ) CC(   0) </rsp>
<rsp>DB(DEDBJN03) DG(GROUP1  ) MBR(IMS1    ) CC(   0) </rsp>
<rsp>DB(BE3PARTS) DG(GROUP1  ) MBR(IMS1    ) CC(   0) </rsp>
<rsp>AREA(DB21AR1 ) DG(GROUP1  ) MBR(IMS1    ) CC(   0) </rsp>
<rsp>DG(GROUP1  ) MBR(IMS1    ) CC(   0) </rsp>
</cmdrspdata>
</imsout>

Explanation: The command starts access of all the members of data group, GROUP1, and makes them available. The command response lines are returned for all the databases or areas that are processed with OPTION(ALLRSP) specified.

Example 3 for UPDATE DATAGRP command

TSO SPOC input:
UPDATE DATAGRP NAME(DBGXYZ) START(QUIESCE) OPTION(HOLD)
TSO SPOC output:
DataGroup  DBName   MbrName    CC      
DBGXYZ     DB1XYZ   IM02        0       
DBGXYZ     DB2XYZ   IM02        0       
DBGXYZ              IM02        0       
DBGXYZ     DB1XYZ   IM01        0       
DBGXYZ     DB2XYZ   IM01        0       
DBGXYZ              IM01        0       
DBGXYZ     DB1XYZ   IM03        0       
DBGXYZ     DB2XYZ   IM03        0       
DBGXYZ              IM03        0       

Explanation: This example is of a successful quiesce-and-hold for a data group.

Example 4 for UPDATE DATAGRP command

TSO SPOC input:
UPD DATAGRP NAME(DBGXYZ) START(QUIESCE)
TSO SPOC output:
DataGroup  DBName   MbrName    CC     
DBGXYZ     DB1XYZ   IM02        0     
DBGXYZ     DB2XYZ   IM02        0     
DBGXYZ              IM02        0     
DBGXYZ     DB1XYZ   IM01        0     
DBGXYZ     DB2XYZ   IM01        0     
DBGXYZ              IM01        0     
DBGXYZ     DB1XYZ   IM03        0     
DBGXYZ     DB2XYZ   IM03        0     
DBGXYZ              IM03        0     

Explanation: This example is of a successful quiesce-and-go for a data group.

Example 5 for UPDATE DATAGRP command

TSO SPOC input:
UPD DATAGRP NAME(DBGXYZ)  STOP(QUIESCE)
TSO SPOC output:
DataGroup  DBName   MbrName    CC    
DBGXYZ     DB1XYZ   IM02        0     
DBGXYZ     DB2XYZ   IM02        0     
DBGXYZ              IM02        0     
DBGXYZ     DB1XYZ   IM01        0     
DBGXYZ     DB2XYZ   IM01        0     
DBGXYZ              IM01        0     
DBGXYZ     DB1XYZ   IM03        0     
DBGXYZ     DB2XYZ   IM03        0     
DBGXYZ              IM03        0     

Explanation: This example is of releasing the quiesce for a data group.