- Page 1 - ------------------------------------------------------------------- | README file for DRV V02.2A | | Edition: 06.11.2002 | ------------------------------------------------------------------- This file describes the changes/extensions of DRV V02.2A The changes/extensions refer to the following manual DRV V02.0A Edition December 1996 Order number: U6515-J-Z125-3-7600 References to chapters and sections in this README file are to the above manual. Contents -------- 1. Processing original and mirror disks separately .......... Page 2 2. START-DRV-DUAL-MODE ...................................... Page 7 3. STOP-DRV-DUAL-MODE ....................................... Page 12 A - Page 2 - 1. Processing original and mirror disks separately (New section: 4.5 "Processing original and mirror disks separately" in the manual (see above) on page 28ff.) Usage scenarios --------------- Saving during operation At a particular consistency point (the pubset has been exported with EXCAT) all disk pairs of the pubset are separated and the mirror disks are renamed. This allows the "normal" application to continue accessing and modifying the data. The files on the mirror pubset are saved with ARCHIVE or HSMS. You must thereby note that it is not possible to make an incremental backup in this way: the relevant indicator in the file catalog showing that the file has been saved is only written to the catalog of the mirror file. When the drives are rejoined, this catalog is always taken over from the original pubset and the saved files then appear not to have been saved. With a full save, you must also note that migrated files on the mirror pubset cannot be saved as HSMS only knows the original file names. If it is only necessary to save the time required for the save, concurrent copy should be used (requires HSMS). After a brief initialization, concurrent copy can save in parallel to the normal application without having to separate the DRV pairs. It must be noted that additional space is required on the disk if large numbers of changes are involved and this leads to either an increase in saving times or a decrease in the performance of the applications. In contrast to saving with DRV, the consistency point is only reached at the end of a successful save with concurrent copy. If problems occur during saving, it will have to be repeated at a later time. Parallel application on the same data A bank has a booking system, e.g. for cash dispensing machines with a large amount of data, which must have high availability (no failures, used 23 hours per day). We will call the pubset "A". Accounting must be performed at the end of the month, but the data must be available as soon as possible, e.g for new bookings. Since accounting takes several hours, it has to be done using a copy of the data. Copying via a command or using the database takes far too long as the amount of data is fairly large. The copy can be made in, say, 20 minutes by separating the DRV disks (/EXCAT A, /STOP-DRV and renaming them, /IMCAT A, /IMCAT B). The booking system is available again after this time. A - Page 3 - After the accounting run is finished, only the booking system data that has been modified in the meantime is copied, i.e. 10 MB instead of 20 GB. This only puts a minor load on the booking system. Schematic illustration of the process The designations below are used in the following sections: - Original application: Application(s) which normally (e.g. during the day) work with the data which is made highly available with DRV. - Original pubset: A pubset mirrored with DRV. "A" is used as the catalog ID in the example. - Mirror pubset: Pubset made up of the "separated" and renamed mirror disks. It contains the same data as the original pubset at the time of separation. - Secondary application: Application(s) which run on the mirror pubset. These can be saves or evaluations. The applications modify the data only slightly or not at all. The evaluation results are written to a third pubset as the changes on the mirror pubset are lost when the original pubset is rejoined to it. - Monitoring the pubset with DRV: DRV uses main memory to note which areas of the original and mirror pubsets were modified. This information is evaluated during rejoining. Sequence: - The original application is terminated - The original pubset is exported with EXCAT - /STOP-DRV PUBSET=A,NEW-NAME-OF-REMOVED=B The command executes the following actions: - Check that all disks of the pubset are connected, unallocated and in DRV-DUAL mode - Transition to DRV-MONO. The mirror disks are temporarily in the DUAL-CRASHED state - Special allocation of the mirror disks - Rename the VSN in the SVL, volume catalog and file catalog of the mirror disks - Set the DRV-MONO indicator in the SVL of the mirror disks - Set the monitoring indicator for all original and mirror disks - Release the allocations of the mirror disks - If necessary, create an MRSCAT entry for the mirror pubset If the command has executed successfully, the two pubsets "A" and "B" now exist and both contain the same data. Changing the catalog ID on the mirror disks from A to B now makes all the original pubset files accessible separately with the catalog ID "B". A - Page 4 - If errors occur, the mirror disks do not contain consistent data and are marked accordingly, and the data cannot be accessed. The disks must be reinitialized manually by systems support with the original VSN. The DRV-DUAL state can then be restored with /START-DRV-DUAL-MODE FROM-PUBSET=*CURRENT,TO-PUBSET=A and the /STOP-DRV-DUAL-MODE PUBSET=A,TO-PUBSET=B command repeated. - The original and mirror pubsets are imported with IMCAT by systems support. - Since both pubsets are operated in DRV-MONO mode, DRV can start monitoring the pubsets for changes. It uses main memory to store the information on which blocks are modified. - Operate the original applications and secondary application - Terminate the secondary application - /START-DRV FROM-PUBSET=A,TO-PUBSET=B The command executes the following actions: - Tests: Both pubsets contain the same number of disks of the same type and DRV pairs can be formed with all disks (type, configuration and formatting are identical). - Export the mirror pubset with EXCAT - Special allocation of the mirror pubset disks - Change the VSN in the SVL of the mirror disks - Release the mirror pubset disks - The metadata is copied for each disk - If the tests were positive, the modified files are determined from the monitoring data and copied. Otherwise, all allocated blocks are copied. If the command was completed successfully, the original state has now been restored: the original pubset is held highly available by DRV and the original application is running. If errors occur, systems support must reinitialize the disks with the original VSNs (PUBAxx) and copy them with /START-DRV-DUAL-MODE FROM-PUBSET=*CURRENT,TO-PUBSET=A. A - Page 5 - Graphical illustration: ------------------------------------------------------------------ | | | ----- ------------------------------------ | | | | | 1. Stop the original application | | | ----- | | 2. EXCAT A | | | ----->| | | | 3. STOP-DRV PUBSET=A,NEW-NAME=B | | | | | |--- ------------------------------------ | | | | | | DRV pair | | | ----- | pubset A | | | | | | | | | | | | | v v ------------------- ------------------ | | | ----- ----- | 4a. IMCAT A | | 4b. IMCAT B | | | | | | | | | 5b. Start the | | 5b. Start the | | | | | | | | | original | | secondary | | | | | | | | | application | | application| | | | ----- ----- ------------------- ------------------ | | | Pub- | | Pubset B | | | set | | | | | A | | | | | | | | | | | | | | | | | | | | v v -------------------------------------- | | | ----- ----- | 6. Stop the secondary application | | | | | | | | | 7. START-DRV FROM-PUBSET=A, | | | -----| |->| | | TO-PUBSET=B | | | | | | | -------------------------------------- | | ----- ----- | | | | DRV pair | | pubset A: | | reconstruction | | | ------------------------------------------------------------------ General conditions Certain general conditions and procedural specifications must be satisfied in order to use the new DRV functionality. Most of the conditions can be easily fulfilled, simply because they are necessary for productive operation. Additional specifications are for process security. General conditions for optimum performance The time required for reconstruction when rejoining depends on the amount of modified data involved. The performance can be improved with the following parameters: - original and mirror pubsets in different disk subsystems - separation, separate processing and rejoining during a low activity period - optimum performance of saving and secondary application to minimize the separation period (possibly at the cost of main application throughput) A - Page 6 - Restrictions - Only SF (single-feature) pubsets are supported. Private disks cannot be "renamed" as the catalog entries may be stored in several pubsets. For SM (system-managed) pubsets, DRV only supports mirroring of separate volume sets. The files on these volume sets can, however, not be renamed if they remain in the same SM pubset. It is, of course, possible to separate private disks or SM pubsets whose volume sets are all mirrored with DRV, and process them in another system. In this case, DRV cannot copy the modified blocks when rejoining, but must copy all allocated blocks as previously. - The catalog ID of the mirror pubset must have the same length as the original pubset. Actions allowed during separated processing - Import original and mirror pubset. - Change the data on the original pubset: modify, delete, create migrate or reread files or JVs. - Change the data on the mirror pubset: files can (theoretically) be deleted, modified or created. However, all changes are lost during rejoining! HSMS can be used for migrating and rereading files, but there is no point in this as the pubset only exists during the separation phase. Saved files are no longer usable after rejoining. Evaluation programs which work on the mirror pubset must store their results on other (original or third) pubsets. - Process the mirror pubset on another computer (virtual, native): In this case, DRV cannot store any information on modified data. For rejoining, the mirror pubset must be reimported with IMCAT to the computer on which the original pubset is operational. DRV then tries to determine which files have been modified on the mirror pubset from its catalog. These are then completely reconstructed. Actions not allowed during separated processing - Process the mirror pubset on another machine: the system on which the mirror pubset is processed and the one on which the subsequent reconstruction takes place must have exactly the same system time, as the modification time is relevant in the mirror pubset catalog. Special applications such as DPAGE, SIR-IP, diagnostic programs or FDDRL must not be used on the mirror pubset. - Unload and reload the DRV subsystem. - Change the disk configuration: disks must not be removed or added with /MODIFY-PUBSET-PROCESSING on either the original or mirror pubset. A - Page 7 - 2. START-DRV-DUAL-MODE (Replace in section 7 the command "START-DRV-DUAL-MODE", in the manual on page 92) START-DRV-DUAL-MODE Start dual recording Domain: DEVICE Privileges: TSOS OPERATING Routing code: D Function The /START-DRV-DUAL-MODE command starts dual recording. The RECORDING-MODE parameter is set implicitly to DRV and the disks belonging to the disk pair are updated to the same state. If a disk pair is formed for the first time from two SRV disks, the disks may not be allocated and only the SVLs (Standard Volume Labels) are updated. The allocation is of no consequence when changing from mono to dual operation. /START-DRV-DUAL-MODE normally initiates either a reconstruction or equalization. If the syntax FROM-PUBSET=,TO-PUBSET= is used, all disks in the mirror pubset are renamed to disks of the original pubset. A prerequisite for this is that the mirror pubset was created with /STOP-DRV-DUAL-MODE ...,NEW-NAME-OF-REMOVED. Notes: - All accessed disks must be mounted. The operator can use the /SHOW-DRV-STATUS command to determine which disks are mounted or free (UNIT=*SELECT(RECOVER-STATE=*NONE)). - SRV disks may not be allocated. - If the mirror pubset was only operated on one computer and in one session, only the data modified on the original and mirror disks is copied, i.e. the current state of the original pubset is copied to the mirror pubset. This nullifies all changes made to the mirror pubset since the separation. If the mirror pubset was used in the meantime on another computer, all modified data on the original pubset and all modified or deleted files on the mirror pubset are copied to the mirror pubset. A - Page 8 - Format ----------------------------------------------------------------------- | START-DRV-DUAL-MODE | |---------------------------------------------------------------------| | VOLUME= *BY-UNIT(...) / *BY-PUBSET(...) / list-poss(10): | | -------- | | | | *BY-UNIT(...) | | | | | | FROM-UNIT = *CURRENT / / | | | -------- | | | | | |,TO-UNIT = / | | | | *BY-PUBSET(...) | | | | | |FROM-PUBSET = *CURRENT / | | | -------- | | | | | |,TO-PUBSET = | | | ----------------------------------------------------------------------- Operands VOLUME= Defines which disk/pubset pair is to be switched to dual recording. The way the disk pair is specified depends on whether reconstruction, equalization or SVL updating is to be executed. /SHOW-DRV-STATUS can be used to determine which action is to be expected when information on the physical disks is requested (INFORMATION=*VOLUMES). If the disks separated with /STOP-DRV-DUAL-MODE PUBSET=,NEW-NAME-OF-REMOVED= are to be rejoined, they must be in DRV-MONO mode and must have been imported. A check is made to determine if these are the same disks that were separated. After command execution, the mirror pubset is exported with EXCAT and its disks transferred to the original pubset, which is then in DRV-DUAL mode again. The original pubset remains imported. The reconstruction may possibly not be completed at the end of command execution. VOLUME=*BY-UNIT(...) ------------- Defines the disk devices for the copy process. *BY-UNIT(...) must be specified if the copy direction has to be determined for equalization or DRV cannot automatically determine the disks. FROM-UNIT= Defines the device to be copied from for a reconstruction or equalization. FROM-UNIT=*CURRENT -------- These cases can be determined from the output of the /SHOW-DRV-STATUS command. It contains the READ and RECONSTRUCT values for the two physical disks in the SVL-INFO column. DRV determines the VSN from the disk mounted on the device specified with TO-UNIT. DRV then finds the read disk automatically from the VSN. A - Page 9 - FROM-UNIT= / Name of the device on which the read disk is mounted. TO-UNIT= / Defines the device to be copied to for a reconstruction or equalization. VOLUME=*BY-PUBSET(...) Defines the original and mirror pubsets for the copy process. FROM-PUBSET=*CURRENT -------- This does not join two pubsets, it starts a reconstruction or equalization for all disks of the pubset specified under TO-PUBSET. All blocks or all allocated blocks are copied. FROM-PUBSET= Name of the catalog ID of the pubset from which the modified blocks are to be copied to the TO-PUBSET. The pubset must be imported in DRV-MONO mode and monitored for changes by DRV. The catalog ID for FROM-PUBSET must have the same length as that for TO-PUBSET. See section "4.5 Processing original and mirror disks separately", on page 2 of this readme file for additional requirements. TO-PUBSET= Name of the catalog ID of the mirror pubset created by the separation or with FROM-PUBSET=*CURRENT of a normal pubset. If two pubsets are to be joined, the one specified in TO-PUBSET must be imported in DRV-MONO mode. All changed data on this pubset is overwritten with the data from the pubset specified under FROM-PUBSET. VOLUME=list-poss(10): VSN of the disk pair for which dual recording is activated. The disk pair can be specified via the VSN in the following cases, which can be seen in the /SHOW-DRV-STATUS output. - A disk pair is formed for the first time from two identical SRV disks. If data exists, this is copied with the FDDRL service. Only the SVLs of the two disks are updated. - An equalization is carried out because the disk pair was allocated at the time of a prior system crash. In this case, the SVL-DRV-INFO column of the SHOW-DRV-STATUS output contains the value DUAL-CRASHED. - An interrupted equalization is restarted. In this case, the SVL-DRV-INFO column of the SHOW-DRV-STATUS output contains the value EQUALIZE for the disk pair write disk and READ for the read disk. - An interrupted reconstruction is restarted. In this case, the SVL-DRV-INFO column of the SHOW-DRV-STATUS output contains the value RECONSTRUCT for the disk pair write disk and READ for the read disk. A - Page 10 - Results and return codes A global termination message (NBR0740) containing the return code is created for console commands. DRV itself creates a termination message for terminal (systems support) commands as the return code is not automatically visible. The command is taken to be processed when all partial jobs have been completed and any subsequent actions (reconstruction, equalization) have been initialized. The results of the subsequent actions are not waited for and do not affect the command result. ---------------------------------------------------------------------- |(SC2)| SC1 | Maincode | Meaning | ---------------------------------------------------------------------- | | 0 | CMD0001 | All partial jobs have been successfully | | | | | processed (termination message DRV0080 on | | | | | the terminal) | | | | | | | 1 | 0 | DRV0043 | All partial jobs have been successfully | | | | | processed, DUAL mode was already set, no | | | | | actions | | | | | | | | 1 | DRV0030 | Syntax error, | | | | | e.g. The catalog ID is not of the same | | | | | length for FROM-PUBSET and TO-PUBSET | | | | | | | | 32 | DRV0084 | Internal error, command aborted | | | | | | | | 64 | DRV0040 | One or both disk(s) not available | | | | | | | | 64 | DRV0041 | VSN on the two MNs different | | | | | | | | 64 | DRV0042 | FROM-MN and TO-MN or FROM-PUBSET and | | | | | TO-PUBSET are the same | | | | | | | | 64 | DRV0044 | No two disks | | | | | | | | 64 | DRV0045 | VSN specification insufficient | | | | | | | | 64 | DRV0051 | Disk is in SRV recording mode | | | | | | | | 64 | DRV0055 | DRV disk pair cannot be formed | | | | | | | | 64 | DRV0059 | Device not usable as paging is still | | | | | enabled on another device | | | | | | | | 64 | DRV0081 | Command partially successful | | | | | | | | 64 | DRV0082 | Command unsuccessful | | | | | | | | 64 | DRV0085 | Prerequisites not fulfilled (enter reason | | | | | as insert 2) | | | | | | | | 64 | DRV0086 | Processing error (enter reason as insert 2) | | | | | | | | 65 | CMD2241 | Command not available as the DRV subsystem | | | | | is not loaded | | | | | | ---------------------------------------------------------------------- A - Page 11 - ---------------------------------------------------------------------- |(SC2)| SC1 | Maincode | Meaning | ---------------------------------------------------------------------- | | 130 | DRV0031 | VSN/PVS allocation cancelled, no DRV actions| | | | | | | | 130 | DRV0046 | DRV action already running | | | | | | | | 130 | DRV0052 | VSN/PVS already SRV allocated | | | | | | | | 130 | DRV0053 | VSN already registered as PPD/SPD in NDM | | | | | | | | 130 | DRV0054 | DRV allocation active for disk | | | | | | | | 130 | DRV0083 | Command processing currently not possible | | | | | The wait time cannot be determined, it is | | | | | possible that it does not expire in this | | | | | session. This applies generally for all | | | | | return codes with subcode1 = 130. | ---------------------------------------------------------------------- Rejection grounds with DRV0085 (Insert 2) ---------------------------------------------------------------------- | Text of insert | Meaning | ---------------------------------------------------------------------- | NOT SINGLE FEATURE PUBSET | FROM-PUBSET or TO-PUBSET: | | | pubset type SM or volume set | ---------------------------------------------------------------------- | NOT ALLOCATED OR NOT MONO | FROM-PUBSET or TO-PUBSET: | | | not imported or incorrect DRV or | | | allocation mode (e.g. allocated by | | | paging) | ---------------------------------------------------------------------- | COPY-PUBSET DOES NOT MATCH | FROM-PUBSET and TO-PUBSET do not | | VOLUMES DO NOT MATCH | contain the same number of disks or| | | DRV state of at least one disk pair| | | has been changed since switchoff | ---------------------------------------------------------------------- | VOLUME NOT MONITORED | One or more of the FROM-PUBSET | | | disks not being monitored | ---------------------------------------------------------------------- | NOT ORIGINAL PUBSET | FROM-PUBSET was not the original | | | pubset with /STOP-DRV-DUAL-MODE | ---------------------------------------------------------------------- | CANNOT OCCUPY PUBSET | FROM-PUBSET or TO-PUBSET cannot | | | be allocated (possibly incorrect | | | pubset state) | ---------------------------------------------------------------------- | EXCAT NOT FINISHED | The export process for TO-PUBSET | | | is not completed in the specified | | | time | ---------------------------------------------------------------------- | NOT SF PUBSET / VOLSET | With syntax FROM-PUBSET=*CURRENT: | | | Only SF pubsets or volume sets are | | | possible | ---------------------------------------------------------------------- | NOT FOUND OR WRONG ALLOCATION | With syntax FROM-PUBSET=*CURRENT: | | | Pubset not found or incorrectly | | | allocated | ---------------------------------------------------------------------- A - Page 12 - 3. STOP-DRV-DUAL-MODE (Replace in section 7 the command "STOP-DRV-DUAL-MODE", in the manual on page 96) STOP-DRV-DUAL-MODE Stop dual recording Domain: DEVICE Privileges: TSOS OPERATING Routing code: D Function: The /STOP-DRV-DUAL-MODE command switches from dual to single recording. It removes the specified disk, identifies it as inconsistent and sets mono mode. A running reconstruction or equalization is immediately aborted. /STOP-DRV-DUAL-MODE can be called regardless of whether the disk pair is allocated or not. A reconstruction, which copies the complete disk, is always required to enable a later change back to dual mode. Only change to mono mode if it is absolutely necessary or if single recording is to be used permanently. The syntax PUBSET=,NEW-NAME-OF-REMOVED= is used to generate a second (mirror) pubset from the original pubset, with the catalog ID specified with NEW-NAME-OF-REMOVED. Both pubsets are in DRV-MONO mode after the command is executed. DRV takes over the functions of the utility PVSREN for renaming the disks and file names in the catalog. The requirements described in "Processing original and mirror disks separately" must be fulfilled (see page 2 of this readme file). Notes: - All accessed disks must be mounted. The operator can use the /SHOW-DRV-STATUS command to determine which disks are mounted or free (UNIT=*SELECT(RECOVER-STATE=*NONE)). - At least one disk of the disk pair must be available. The /SHOW-DRV-STATUS command can be used to determine which disks are not available (UNIT=*SELECT(RECOVER-STATE=*SUSPENDED)). - A disk which is being used by paging and has been removed with /STOP-DRV-DUAL-MODE is not released, it continues to be used for paging. The effect is that all user data and the system metadata is operated further in mono mode on the remaining disk. The paging area on the removed disk can only be released with the /REDUCE-PAGING-AREA command. - A disk which has been removed with /STOP-DRV-DUAL-MODE and is to be replaced by another disk should be written with another VSN with the VOLIN utility. Otherwise, ambiguities can occur and, e.g the "old" disk could be selected automatically in the home pubset during startup. A - Page 13 - Format ----------------------------------------------------------------------- | STOP-DRV-DUAL-MODE | |---------------------------------------------------------------------| | VOLUME= *BY-UNIT(...) / *BY-PUBSET(...) / list-poss(10): | | | | *BY-UNIT(...) | | | | | | UNIT = / | | | | *BY-PUBSET(...) | | | | | | PUBSET = | | | | | |,NEW-NAME-OF-REMOVED = / *SAME | | | ----------------------------------------------------------------------- Operands VOLUME= Defines which disk pair is to be switched to dual recording. VOLUME = *BY-UNIT(...) The disk of the specified disk device is to be removed. UNIT = / Name of the device on which the disk is mounted. The disk device must be specified if DRV cannot determine it automatically. The command is rejected if DRV can determine the disk itself and the disk device is still specified. VOLUME = *BY-PUBSET All disks of the specified pubset are to be set to the DRV-MONO state. The removed disks are either converted into a new pubset or not, depending on the value specified with NEW-NAME-OF-REMOVED. PUBSET = Name of the pubset whose disks are to be set to DRV-MONO. If the mirror disks are to be renamed, all disks must be in DRV-DUAL mode and the pubset exported. Only SF pubsets can be renamed. NEW-NAME-OF-REMOVED = Name of the pubset that is to be created from the disks removed from the pubset specified in PUBSET. No disks may exist for this pubset before the command is called. If the catalog ID is entered in the MRSCAT, it is taken over as long as the pubset type matches (SF). The catalog ID must have the same length as that specified in PUBSET. NEW-NAME-OF-REMOVED = *SAME The removed mirror disks are not renamed and remain in the DUAL-CRASHED state. This form can be used to specify all volumes in a pubset instead of a list of VSNs. A - Page 14 - VOLUME = list-poss(10): VSN of the disk pair to be switched to single recording. In this case, DRV must be able to determine which disk is to be removed. The disk pair must be specified via the VSN in the following cases as DRV determines the disk automatically: - A REMOUNT message is still open for one of the two disks. DRV removes this disk. - An equalization is currently in progress. DRV removes the drive being copied to. - A reconstruction is currently in progress. DRV removes the drive being copied to. /SHOW-DRV-STATUS outputs these case if the summary information is queried (INFORMATION=*SUMMARY). Results and return codes A global termination message (NBR0740) containing the return code is created for console commands. DRV itself creates a termination message for terminal (systems support) commands as the return code is not automatically visible. The command is taken to be processed when all partial jobs have been completed and any subsequent actions (reconstruction, equalization) have been initialized. The results of the subsequent actions are not waited for and do not affect the command result. ---------------------------------------------------------------------- |(SC2)| SC1 | Maincode | Meaning | ---------------------------------------------------------------------- | | 0 | CMD0001 | All partial jobs have been successfully | | | | | processed (termination message DRV0080 on | | | | | the terminal) | | | | | | | 1 | 0 | DRV0047 | All partial jobs have been successfully | | | | | processed, MONO mode was already enabled, | | | | | no actions | | | | | | | | 1 | DRV0024 | Catalog IDs for PUBSET and | | | | | NEW-NAME-OF-REMOVED are identical | | | | | | | | 1 | DRV0030 | Syntax error: | | | | | Catalog IDs for NEW-NAME-OF-REMOVED and | | | | | PUBSET are not of the same length | | | | | NEW-NAME-OF-REMOVED=PUB is not allowed | | | | | | | | 32 | DRV0084 | Internal error, command aborted | | | | | | | | 64 | DRV0040 | One or both disk(s) not available | | | | | | | | 64 | DRV0044 | No two disks | | | | | | | | 64 | DRV0045 | VSN specification insufficient | | | | | | | | 64 | DRV0051 | Disk is in SRV recording mode | | | | | | | | 64 | DRV0057 | No DRV disk | | | | | | | | 64 | DRV0058 | VSN specification is not unique or the | | | | | device cannot be removed | | | | | | | | 64 | DRV0059 | Device is in use by paging | | | | | | ---------------------------------------------------------------------- A - Page 15 - ---------------------------------------------------------------------- |(SC2)| SC1 | Maincode | Meaning | ---------------------------------------------------------------------- | | 64 | DRV0081 | Command partially successful | | | | | | | | 64 | DRV0082 | Command unsuccessful | | | | | | | | 64 | DRV0085 | Prerequisites not fulfilled (enter reason | | | | | as insert 2) | | | | | | | | 64 | DRV0086 | Processing error (enter reason as insert 2) | | | | | | | | 65 | CMD2241 | Command not available as the DRV subsystem | | | | | is not loaded | | | | | | | | 130 | DRV0031 | VSN/PVS allocation cancelled, no DRV actions| | | | | | | | 130 | DRV0046 | DRV action running | | | | | | | | 130 | DRV0052 | VSN/PVS already SRV allocated | | | | | | | | 130 | DRV0053 | VSN already registered as PPD/SPD in NDM | | | | | | | | 130 | DRV0054 | DRV allocation active for disk | | | | | | | | 130 | DRV0083 | Command processing currently not possible | | | | | The wait time cannot be determined, it is | | | | | possible that it does not expire in this | | | | | session. This applies generally for all | | | | | return codes with subcode1 = 130. | ---------------------------------------------------------------------- Rejection grounds with DRV0085 (Insert 2) ---------------------------------------------------------------------- | Text of insert | Meaning | ---------------------------------------------------------------------- | NOT SINGLE FEATURE PUBSET | PUBSET: | | | pubset type SM or volume set | ---------------------------------------------------------------------- | ALLOCATED OR NOT DUAL | PUBSET: | | | imported or incorrect DRV or | | | allocation mode | ---------------------------------------------------------------------- | LV NOT FREE | PUBSET: | | | allocation exists (possibly | | | cancelled via EXCAT, FORCE or | | | after /DETACH, FORCE=YES) | ---------------------------------------------------------------------- | ONLINE | NEW-NAME-OF-REMOVED: | | | some disks are online | ---------------------------------------------------------------------- | CATALOG INCONSISTENT | PUBSET: | | | file catalog $TSOS.TSOSCAT is | | | inconsistent | ---------------------------------------------------------------------- | STOP-DRV NOT FINISHED | PUBSET: | | | DRV-MONO has not been achieved in | | | the necessary time for a volume | ---------------------------------------------------------------------- A - Page 16 - ---------------------------------------------------------------------- | Text of insert | Meaning | ---------------------------------------------------------------------- | NOT SF PUBSET / VOLSET | With syntax FROM-PUBSET=*CURRENT: | | | Only SF pubsets or volume sets are | | | possible | ---------------------------------------------------------------------- | NOT FOUND OR WRONG ALLOCATION | With syntax | | | NEW-NAME-OF-REMOVED=*SAME: | | | pubset not found or is incorrectly | | | allocated | ----------------------------------------------------------------------