Messages SVM4000 through SVM4999
This group includes messages for the (formerly MainView Storage) MainView SRM product.
Number | Description |
|---|---|
SVM4000I | job,step,dd ATTEMPTING action FOR dsn,vol,extent Explanation: This message is the first written to the log during a StopX37/II recovery attempt. The action field describes the type of recovery being attempted. The variable fields are
User response: No action is necessary. |
SVM4001I | RECOVERY ATTEMPT FAILED TO PASS FLST/RLST CRITERIA Explanation: The job/DSN did not satisfy the filter or rule list criteria specified for the recovery type being attempted. The recovery type was listed in the preceding SVM4000I message. User response: If you prefer that this job/DSN be recovered, the filter or rule lists must be modified to select the job/DSN for recovery. The reason for the FLST/RLST failure can be determined by specifying TRACE=YES for the job/DSN in the appropriate SMMDIAGxx member and rerunning the job. |
SVM4003I | svos NOT ACTIVE, function UNABLE TO PROCESS Explanation: The Started Task (SVOS) is no longer active and the specified function is not valid. This message is generated when the HOOKONLY command is issued to stop the Started Task, while leaving the BMC AMI Storage Allocationor X37II hooks active. is not able to perform the specified function. User response: Start to allow full functionality of BMC AMI Storage Allocation (or X37II). |
SVM4100I | PRIMARY NOT REDUCED FOR KEYRANGE CLUSTER dsn Explanation: The allocation component cannot perform primary space reduction for ICF VSAM clusters defined with key ranges. User response: No action is necessary. |
SVM4101I | UNABLE TO REDUCE PRIMARY RC = returnCode, RSN = reasonCode Explanation: The allocation component was unable to reduce the primary space allocation. The returnCode (RC) and reasonCode (RSN) are returned by VSAM. User response: Examine the catalog return code and reason code to determine why the DEFINE failed. The return code and reason code can be found in the IBM System Messages and Codes Manual under message IDC3009I. |
SVM4102I | UNABLE TO REDUCE PRIMARY, REASON=NO SPACE FPL Explanation: The allocation component was unable to reduce the primary space allocation because the space parameter on the IDCAMS DEFINE could not be determined. User response: Contact BMC Software Customer Support. |
SVM4103I | PRIMARY SPACE REQUEST WENT TO ZERO DSN=dsn Explanation: StopX37/II reduced the primary space request until it reached zero. Primary allocations of zero are not allowed for VSAM or partitioned data sets. The data set cannot be allocated. User response: Increase space available to the data set. |
SVM4104I | PRIMARY SPACE REQUEST WENT BELOW LIMIT DSN= dsn Explanation: The allocation component reduced the primary space request for a data set past the floor limit specified in the SPACPRIM keyword in the SPACPRIM RLST. The data set will not be allocated. This messages is issued for VSAM as well as non-VSAM data sets. User response: Increase space available to the data set or reduce the floor limit specified in the RLST. |
SVM4105E | UNABLE TO SCRATCH/RENAME; REASON = reason Explanation: StopX37/II was unable to scratch or rename the data set for the reason indicated. User response: Examine the text to see why the operation could not be performed. |
SVM4106S | action FAILED FOR DSN= dsn (RC- returnCode - reasonCode) Explanation: The catalog management function being performed by the allocation component failed. The return code and reason code were returned by catalog management. User response: Examine the catalog return code and reason code to determine why the operation failed. The return code and reason code can be found in the IBM System Messages and Codes Manual under message IDC3009I. |
SVM4107S | GETMAIN FAILED FOR CPL LOCATE WORK AREA Explanation: A GETMAIN failed when trying to obtain space for a catalog parameter list (CPL) control block. The recovery will be terminated. User response: Increase the region size and rerun the job. |
SVM4108S | CANDIDATE VOLUME DETECTED IN CATALOG DURING SPACVOLA PROCESSING Explanation: During SPACVOLA processing for an SMS-managed data set, an existing candidate volume (******) was found in the catalog that indicates that the data set should have already extended to a new volume without the allocation component. The recovery will be terminated. User response: Attempt to determine why the data set did not extend to a new volume in the storage group. |
SVM4109S | DUPLICATE VOLUME DETECTED IN CATALOG DURING SPACVOLA PROCESSING Explanation: During SPACVOLA processing for an SMS-managed data set, the same volume was found twice in the existing data set list. The recovery will be terminated. This message will be followed by message SVM4110S, which indicates the failing data set. User response: This error is severe. Contact BMC Software Customer Support. |
SVM4110S | DETECTED FOR DSN= dsn Explanation: This message lists the data set name associated with the preceding SVM4109S message. User response: See SVM4109S. |
SVM4111I | dsn RENAMED TO dsn Explanation: NOCATLG2=RENAME was specified in the NOCATLG2 RLST, and the allocation component recovered the data set by renaming the old data set using the second-level qualifier in the NOCATPFX operand in the SMMSYSxx member of parmlib. User response: No action is necessary. |
SVM4112S | UNABLE TO RENAME - INVALID NOCATPFX: dsn Explanation: NOCATLG2=RENAME was specified in the NOCATLG2 RLST. The allocation component attempted to rename the data set, but the second-level qualifier in the NOCATPFX operand in the SMMDIAGxx member of parmlib was invalid. User response: The NOCATPFX operand must be a valid second-level qualifier. |
SVM4113I | ASSIGNED OVERFLOW vol TO SATISFY PRIMARY REQUEST FOR dsn Explanation: StopX37/II detected an error for insufficient space on the volser passed by the IDCAMS utility program during catalog of a VSAM data set (dsn). The SPACPRIM function was able to recover the allocation by locating a DASD volume (vol) in an overflow storage group that had sufficient space to satisfy the original primary request. There was no need to reduce the primary amount. This message is typically followed by the IGD17223I message to indicate that the data set was allocated to an overflow storage group. User response: No action is necessary. |
SVM4114I | PRIMARY SPACE REQUEST WENT BELOW LIMIT Explanation: The allocation component reduced the primary space below the floor limit specified in the SPACSWIR RLST. The primary space for a VSAM file was reduced during SPACVOLA processing by the percentage specified in the SPACSWIR RLST until it was below the floor limit. The data set will not be recovered. User response: Either provide more space for the data set or lower the floor limit specified in the SPACSWIR RLST and rerun the job. |
SVM4115I | PRIMARY SPACE REQUEST WENT TO ZERO Explanation: The allocation component reduced the primary space request to zero, and the request still failed. Because primary allocations of zero are allowed by z/OS, failure occurred for another reason: the VTOC was full or a DADSM exit failed the request. User response: No action is necessary. |
SVM4116I | SECONDARY SPACE REQUEST WENT BELOW LIMIT OR TO ZERO Explanation: The allocation component reduced the secondary space below the floor limit specified in the SPACSWIR RLST or to zero. The secondary space for an SMS file was reduced during SPACVOLA processing by the percentage specified in the SPACSWIR RLST until it was below the floor limit or until it went to zero. The data set will not be recovered. User response: Either provide more space for the data set or lower the floor limit specified in the SPACSWIR RLST and rerun the job. |
SVM4117I | job,step,dd,dsn PRIMARY SPACE REDUCED orga / newa units Explanation: The allocation component has reduced the original primary space allocation (orga) to the new allocation (newa). The allocation was requested in units of CYL, TRK, BLK, MAV, KAV, or AVG (units). User response: No action is necessary. |
SVM4118I | REDUCED SECONDARY SPACE FROM nnnn units TO nnnn Explanation: During SPACVOLA processing to add a new volume to an SMS-managed data set, there was not sufficient space to hold the secondary space on any volume in the storage group. However, the job/dsn passed the SPACSWIR FLST/RLST filtering; therefore, the allocation component reduced the original secondary space to the amount listed in the message. The message also shows the space units in which the data set was allocated. User response: No action is necessary. |
SVM4119I | SPACPRIM SPACE REDUCTION AVOIDED. VOLSER vol1 REPLACED WITH vol2 Explanation: During SPACPRIM recovery, was able to locate another volume (vol2) in the DFSMS storage pools to satisfy the original primary request and space reduction was avoided. When SPACPRIM recovery takes place during a catalog service call, the IDCAMS utility program can pass a SMS volume (vol1) with insufficient space in the catalog parameter list. If the global parameter SPACPRIMACS is set to YES, will locate the volume with the largest available extent in the DFSMS storage pool(s) to recover the error. In this instance, found another volume (vol2) with sufficient space to satisfy the original space request and SPACPRIM altered the volume in the catalog parameter list without a need to reduce the primary. User response: No action is necessary. |
SVM4120I | DATA SET WILL BE RECATALOGED FROM VOLUME oldVol TO VOLUME newVol Explanation: The user specified NOCATLG2=UNCATLG in the NOCATLG2 RLST, and the allocation component recovered the data set by uncataloging the old data set on oldVol and forcing z/OS to recatalog the new data set on newVol. The job will be completed with normal return codes, but careful examination will show a RECATALOGED message for a non-SMS data set. User response: No action is necessary. |
SVM4121I | DATA SET WAS SCRATCHED ON VOLUME oldVol AND WILL BE RECATALOGED ON VOLUME newVol Explanation: The user specified NOCATLG2=DELETE in the NOCATLG2 RLST, and the allocation component recovered the data set by deleting the old data set on oldVol and cataloging the new data set on newVol. User response: No action is necessary. |
SVM4122W | SCRATCH FOR DATA SET ON VOLUME volume FAILED (RC= returnCode - reasonCode - diagnosticCode) Explanation: The user specified NOCATLG2=DELETE in the NOCATLG2 RLST, but the allocation component was unable to scratch the old data set. The scratch returnCode, reasonCode, and diagnosticCode are displayed in the message. User response: Contact BMC Software Customer Support and have the return code, reason code, and diagnostic code listed in the message available. |
SVM4123I | JOB name WILL BE FLUSHED Explanation: The user specified NOCATLG2=FLUSH in the NOCATLG2 RLST, and the allocation component has set the job to flush. User response: No action is necessary. |
SVM4124I | CANCEL COMMAND ISSUED FOR JOB name Explanation: The user specified NOCATLG2=CANCEL in the NOCATLG2 RLST, and the allocation component has issued the CANCEL command to cancel the job. User response: No action is necessary. |
SVM4125S | ENTER NOCATLG2 OPTION FOR DSN= dsn, CVOL= curVol,NVOL= newVol Explanation: The user specified NOCATLG2=OPER in the NOCATLG2 RLST, and the allocation component has issued this SVM4125S message to ask the operator to supply the NOCATLG2 option that should be used to perform the NOCATLG2 process. User response: This message will be followed by message SVM4155I. See the user response for that message for possible responses. |
SVM4126S | NOCATLG2 NOT ALLOWED DUE TO NOCATVOL=DIFF Explanation: The user specified NOCATLG2=DELETE or NOCATLG2=RENAME but also specified NOCATVOL=DIFF in SMMSYSxx, which indicates that the allocation component should not perform NOCATLG2 processing if the old and new data sets have the same volume list. In this case the old and new data sets do have the same volume lists; therefore, the allocation component has terminated the recovery. User response: Change SMMSYSxx to specify NOCATVOL=SAME, rerun the job, or correct the job and rerun. |
SVM4127S | UNCATALOGED DATASET EXISTS ON TARGET VOLUME volume Explanation: During NOCATLG2=DELETE processing, the allocation component discovered that an uncataloged data set with the same name as the data set being processed exists on the target volume. The allocation component will not delete this data set because it might not be the one the user intended to delete. The recovery will terminate. User response: Resolve the problem with the uncataloged data set and rerun the job. |
SVM4128S | NOCATLG2=UNCATLG/RENAME FOR SMS DATASET, BUT NEW ALLOCATION FAILED Explanation: NOCATLG2=UNCATLG/RENAME was specified in the NOCATGL2 RLST, and the allocation component tried to uncatalog or rename the existing data set. However, the new data set could not be allocated for some reason. The allocation component, therefore, recataloged or renamed the original data set so that no action was taken. User response: Determine why the new allocation failed and rerun the job. |
SVM4129S | NOCATLG2=UNCATLG/DELETE/RENAME FOR SMS DATASET BUT NOCATSMS=NO Explanation: NOCATLG2=UNCATLG/DELETE/RENAME was specified in the NOCATLG2 RLST, but NOCATSMS=NO was specified in SMMSYSxx. The allocation component will not perform any processing for these options on an SMS-managed data set unless NOCATSMS=YES is specified in SMMSYSxx. User response: Specify NOCATSMS=YES in the appropriate SMMSYSxx member of parmlib and rerun the job. |
SVM4130W | NOCATLG2=DELETE/RENAME FOR SMS DATASET BUT EXISTING DATASET IS NOT DASD Explanation: The allocation component cannot RENAME or DELETE a tape data set. User response: Correct the job and rerun. |
SVM4131S | NOCATLG2=DELETE/RENAME BUT NEW VOLUME = OLD VOLUME. NOCATLG2 FAILED Explanation: NOCATLG2=DELETE/RENAME was specified in the NOCATLG2 RLST, but the old and new volume are the same, and NOCATVOL=DIFF was specified in the SMMSYSxx member of parmlib. NOCATVOL=DIFF indicates that the user only wants NOCATLG2 processing to occur if the volume list for the new data set is different from the volume list for the old data set. Because in this case the volume lists are the same, the recovery is terminated. User response: Either uncatalog the old data set and rerun the job or specify NOCATVOL=SAME in the appropriate SMMSYSxx member of parmlib and rerun the job. |
SVM4132S | NOCATLG2=UNCATLG BUT NEW VOLUME = OLD VOLUME. UNCATLG2 FAILED. NOCATVOL=SAME WILL OVERRIDE Explanation: NOCATLG2=UNCATLG was specified in the NOCATLG2 RLST, but the old and new volume are the same, and NOCATVOL=DIFF was specified in the SMMSYSxx member of parmlib. NOCATVOL=DIFF indicates that the user only wants NOCATLG2 processing to occur if the volume list for the new data set is different from the volume list for the old data set. Because in this case the volume lists are the same, the recovery is terminated. User response: Either uncatalog the old data set and rerun the job or specify NOCATVOL=SAME in the appropriate SMMSYSxx member of parmlib and rerun the job. |
SVM4133W | MAXIMUM NUMBER OF EXTENTS REACHED FOR VSAM DATASET dsn Explanation: VSAM data sets are limited to 251-255 extents. The allocation component (StopX37/II) could not recover this data set because the maximum allowable number of extents was reached. User response: Redefine the data set with more space. |
SVM4134I | USING PRIMARY AMOUNT FOR VSAM SPACVOLA INSTEAD OF SECONDARY. VSAMPRIM=Y,DSN= dsn Explanation: The allocation component did not set the primary space amount for candidate volumes for the VSAM data set to the amount of secondary space. This situation occurred because the user specified VSAMPRIM=Y in the SMMSYSxx member of parmlib. VSAMPRIM defaults to N, which causes the allocation component to set the primary space equal to the secondary for VSAM files so that the initial extent on new volumes will use the secondary amount instead of the VSAM standard of using the primary amount for the initial extent on new volumes. The user has overridden the default by setting VSAMPRIM=Y, which allows VSAM to operate in the standard mode. User response: No action is necessary. |
SVM4135I | DATA SET WILL BE RECATALOGED Explanation: The allocation component has added another volume to a cataloged non-SMS data set. The data set will be recataloged at job termination to add the new volume to the catalog entry. User response: No action is necessary. |
SVM4136S | operation VOLUME FAILED FOR DSN= dsn VOL= volume (RC= returnCode - mn - reasonCode) Explanation: StopX37/II was unable to add {or remove} (operation) the volume (volume) to {or from} the data set (dsn). The VSAM return code and reason code were returned by catalog management module IGGOCLmn as a result of a catalog error or exception condition. User response: Examine message IDC3009I for an explanation of the return codes. Contact BMC Customer Support. |
SVM4137S | NOCATLG2 FAILED FOR DSN= dsn VOL= volume (RC= returnCode - mn - reasonCode) Explanation: The allocation component could not add the volume (volume ) to the data set (dsn). The VSAM return code and reason code were returned by catalog management module IGGOCL mn as a result of a catalog error or exception condition. User response: Examine message IDC3009I for an explanation of the return codes. Contact BMC Software Customer Support. |
SVM4138I | DATA SET HAS BEEN RECATALOGED Explanation: The allocation component SPACVOLA processing has added another volume to a non-SMS data set and has recataloged the data set during SPACVOLA processing. The recatalog is performed during SPACVOLA processing instead of at step termination if the user specifies SCAT=IMMEDIATE in the SMMSYSxx member of parmlib. User response: No action is necessary. |
SVM4139S | UNCATALOG FAILED FOR DSN= dsn VOL= volume (RC= returnCode - mn - reasonCode) Explanation: The allocation component was unable to uncatalog the data set. The return code and reason code were returned by catalog management module IGGOCL mn. User response: Examine the catalog return code and reason code to determine why the uncatalog failed. The return code and reason code can be found in the IBM System Messages and Codes Manual under message IDC3009I. |
SVM4140W | UNABLE TO RECATALOG - GDG BASE ENTRY FOUND FOR DSN= dsn Explanation: The allocation component was attempting to perform NOCATLG2 processing for data set (dsn). However, it was discovered that a GDG base by the same name was already cataloged. The recovery is terminated. User response: Resolve the conflict between the data set (dsn) and the GDG base and rerun the job. |
SVM4141W | ALLOCATION NOT CYLS OR TRKS Explanation: The allocation component SPACSECA processing was attempting to add a secondary space value to a VSAM data set, but the primary allocation was not in cylinders or tracks. The recovery is terminated. User response: Allocate the data set with a secondary or change the primary allocation to use cylinders or tracks and rerun the job. |
SVM4142W | SPACE ALLOCATION IS LESS THAN CA SIZE Explanation: The allocation component SPACSECA processing was attempting to add a secondary space value to a VSAM data set, but the value calculated for the secondary space was less than the size of a control area (CA). The secondary value is calculated by multiplying the primary space amount by the percentage specified in the SPACSECA RLST. A VSAM extent cannot be smaller than the size of a CA. The recovery is terminated. User response: Allocate the data set with a larger primary or increase the percentage specified in the SPACSECA RLST. |
SVM4143W | ALLOCATION NOT CYLS OR TRKS Explanation: The allocation component SPACSWIR processing was attempting to reduce the secondary space value for a VSAM data set during SPACVOLA processing because the new volume did not have enough space, but the data set is not allocated in tracks or cylinders. The recovery is terminated. User response: Allocate the data set in tracks or cylinders or provide more space on the volume for the data set and rerun the job. |
SVM4144W | SPACE ALLOCATION IS LESS THAN CA SIZE Explanation: The allocation component SPACSWIR processing was attempting to reduce the secondary space value for a VSAM data set during SPACVOLA processing because the new volume did not have enough space, but the new value calculated for the secondary space was less than the size of a control area (CA). The new secondary value is calculated by multiplying the original space amount by the percentage specified in the SPACSWIR RLST. A VSAM extent cannot be smaller than the size of a CA. The recovery is terminated. User response: Allocate the data set with a larger primary or increase the percentage specified in the SPACSECA RLST. |
SVM4145W | AFTER PRIMARY REDUCTION SECONDARY SPACE EXCEEDS ORIGINAL PRIMARY SPACE VALUE Explanation: The allocation component SPACSWIR processing was attempting to reduce the secondary space value for a VSAM data set during SPACSECA processing because the new volume did not have enough space, but the new value calculated for the secondary space exceeded the original primary, which was the value already tried, so the new value will not fit on the volume either. The new value is calculated by multiplying the secondary space amount by the percentage found in the SPACSWIR RLST. The recovery is terminated. User response: Provide more space on the volume for the data set or increase the reduction percentage in the SPACSWIR RLST and rerun the job. |
SVM4146I | NOCATLG2=NO WAS SPECIFIED IN RLST. NOCATLG2 FAILED Explanation: NOCATLG2=NO was specified in the NOCATLG2 RLST; therefore, the allocation component did not recover the data set. The job will be completed normally for non-SMS data sets but NOT-CATLGD-2 messages will appear, and for SMS data sets, the job will fail with a JCL error. Subsequent job steps that use the catalog entry will use the old data set or will abend. User response: If the user prefers to recover the job, the NOCATLG2 option should be changed to one that allows recovery. |
SVM4147E | GETMAIN FAILED FOR WORK AREA Explanation: An attempt to build the static area by the allocation component failed. Allocation processing is bypassed for this allocation. User response: Contact BMC Software Customer Support. |
SVM4148E | GETMAIN FAILED FOR WORK AREA Explanation: An attempt to build the static area for the SMS RENAME/DELETE routine failed. The RENAME or DELETE operation will be terminated. User response: Contact BMC Software Customer Support. |
SVM4149E | STOP-X37 STATIC CSECT NOT FOUND Explanation: An attempt to access the static area by the SMS RENAME/DELETE routine failed. The RENAME or DELETE operation will be terminated. User response: Contact BMC Customer Support. |
SVM4150E | INVALID COMMAND Explanation: The SMS RENAME/DELETE routine was passed an invalid command. The RENAME or DELETE operation will be terminated. User response: Contact BMC Customer Support. |
SVM4151W | dsn NOCATLG2 REQUEST FAILED. RECEIVED mm/dd/yy, hh:mm:ss Explanation: The address space (SVOS) was unable to complete a NOCATLG2=DELETE request for another address space in the time allotted (see NOCATTIM global parameter). The message provides the date (mm/dd/yy) and time (hh:mm:ss) SVOS began processing the request. If known, the name of the data set (dsn) needing NOCATLG2 recovery is also provided in the message. If the data set is not known, then '(UNKNOWN DSN?)' will be displayed in the message. This message typically indicates there is some other issue in the system preventing SVOS from processing the NOCATLG2=DELETE request. The date and time provided in the message might prove useful in determining potential system issues when compared to the date and time of the MODIFY command issued by the originating address space found in a SYSLOG. Below is a sample of a MODIFY command issued to SVOS for NOCATLG2 recovery: MODIFY SVOS,'SVALLOC,RECAT,A=00F4FD00,P=7F5061B0,E=7F5061B4, T=000000780000000200000003007F8588' User response: Insure the address space (SVOS) is given high priority in the system. Additional documentation on setting time limits with the NOCATTIM global parameter can be found in the Reference Manual. |
SVM4154I | SECONDARY SPACE REQUEST WENT BELOW LIMIT Explanation: During SPACSECR processing, attempted to reduce the secondary space amount, but the reduced amount falls below the floor limit specified in the SPACSECR RLST. The reduced amount is calculated by multiplying the original secondary space amount by the reduction percentage specified in the SPACSECR RLST. The recovery is terminated. User response: Provide more space on the volume for the data set or lower the floor limit specified in the SPACSECR RLST. |
SVM4155I | REPLY 'IGNORE', 'UNCATLG', 'DELETE', 'FLUSH', 'CANCEL', 'FAIL', OR 'RENAME' Explanation: The user specified NOCATLG2=OPER in the NOCATLG2 RLST, and the allocation component has issued this message to ask the operator to supply the NOCATLG2 option that should be used to perform the NOCATLG2 process. User response: Respond to the message with a valid NOCATLG2 option or IGNORE. An IGNORE response will cause NOCATLG2 processing to abort and the job will be completed with a NOCATLG2 message for non-SMS data sets and a JCL error for SMS data sets. If UNCATLG is specified, the old data set will be uncataloged and the new one will be cataloged properly. If DELETE is specified, the old data set will be scratched and the new data set will catalog properly. If RENAME is specified, the old data set will be renamed using the NOCATPFX value found in SMMSYSxx as the second-level qualifier, and the new data set will be cataloged properly. If CANCEL is specified, the job will be canceled. If FLUSH is specified, the job will be terminated with a JCL error. |
SVM4156W | CANNOT NOCATLG2=RENAME/DELETE FOR DYNAMICALLY ALLOCATED DATASETS. NOCATLG2 FAILED. Explanation: Dynamically allocated data sets cannot be processed by NOCATLG2 if NOCATLG2=RENAME/DELETE. NOCATLG2 processing terminates. User response: No action is necessary. |
SVM4157I | dsname , stepname , ddname, USING xx% OF 4GB VSAM LIMIT Explanation: Describes the percentage of the 4GB limit the VSAM file currently uses. User response: No action is necessary. |
SVM4160I | dataSetName ADJUSTED TO FIT WITHIN 4 GB LIMIT, primary/secondaryAllocationAmt SET TO newAllocationAmtCylinders/Tracks Explanation: Informational message showing that the allocation amount has been changed on a VSAM nonextended data set to fit within the required 4 GB limit. VSAM end-of-volume processing continues with new allocation amounts. User response: No action is necessary. |
SVM4161E | messageText, SVALLOC CONTINUES Explanation: During start of SVALLOC, was not able to install an SVALLOC hook. The messageText provides a description of the failed hook. There might be more than one SVM4161E message to provide additional information about the problem. SVALLOC will continue to process.
User response: Contact BMC Software Customer Support. The messageText will help determine any additional documentation required to debug the problem. In most instances, a DUMPT of the failing zap module will be required. The following zap modules can be found in SYS1.LPALIB:
If messageText indicates 'PATCH AREA IS ALREADY BEING USED', please determine if another allocation product was running in the system. |
SVM4200S | GETMAIN FOR UNIT VERIFICATION ROUTINE FAILED Explanation: The allocation component could not obtain storage for the UCB list. The abending job was extremely short on virtual storage. User response: Increase the REGION parameter. |
SVM4201S | UNKNOWN UNIT TYPE Explanation: An unknown unit type was encountered by the allocation component. User response: Contact BMC Software Customer Support. |
SVM4202S | GETMAIN FOR LTCB FAILED Explanation: The allocation component could not obtain storage for the LTCB control block. The abending job was probably short on private area virtual storage. User response: Increase the region size and retry the job. |
SVM4203W | CANNOT OBTAIN info type INFO FROM CATALOG FOR dsn Explanation: STOPX made a request for data set information residing in the catalog. The CAS (catalog address space) was not able to allocate the catalog in the CAS; therefore, the request for information failed. STOPX processing continues. User response: Examine the CAS to determine if any unusual delays or abends are being seen that could possibly cause the CAS to be nonresponsive. |
SVM4301E | module FAILED WITH RC= @ Explanation: program module failed with the indicated return code. Data Set Size Assist processing discontinues on the current data set. User response: Contact BMC Software Customer Support. |
SVM4400I | VOLUME(S) ADDED - OLD VOLUME vol1, NEW VOLUME vol2 VOLUME COUNT IS nn Explanation: SPACVOLA processing has dynamically added one or more new volumes <vol2> to the data set. Message provides the total number of volumes <nn> for the data set after a successful SPACVOLA. User response: No action is necessary. |
SVM4401W | EXTEND FAILED FOR NONSPECIFIC SMS DATA SET Explanation: The allocation component SPACVOLA added a new volume for the SMS-managed data set, but DFSMS failed to extend to the new volume. User response: Contact BMC Software Customer Support. |
SVM4402I | COMMAND ISSUED TO START procName TO REORG DATASET AFTER SPACVOLA HAS ADDED VOLUMES Explanation: SPACVOLA processing has issued a start command to start the procedure (procName) to copy the data set that has just had volumes added back to a single volume. This is done because the user specified REORG-Y in the SPACVOLA RLST for the data set. User response: No action is necessary. |
SVM4404I | dsn USED CANDIDATE VOLUME FOR STRIPE|S n,n,..,nn Explanation: This message is informational to indicate a multistripe VSAM data set (dsn) extended one or more stripes to another volume. Each stripe requiring another candidate volume will be listed at the end of the message. If more than one stripe used a candidate volume, the stripe numbers will be separated by a comma. Examples: SVM4404I HLQ.MSTRIPE.DATA USED CANDIDATE VOLUME FOR STRIPE 4 SVM4404I HLQ.MSTRIPE.DATA USED CANDIDATE VOLUME FOR STRIPES 2,4,11 User response: No action is necessary. |
SVM4405E | EAS ELIGIBILITY COULD NOT BE DETERMINED Explanation: Code determining EAS eligibility of a requested space allocation failed due to one of the following events: abend occurred (followed by SVC dump), SMS error retrieving SMS construct, or Scheduler JCL Facility (SJF) failure. SVALLOC continues processing. User response: Contact BMC Software Customer Support. In most instances, an SVC dump will be produced and needed to resolve the problem. |
SVM4406S | JFCB EXTENSION FAILURE R15=applicationreturn code, ERROR RC=SWAREQ return code Explanation: An error occurred while processing a JFCB extension. Processing terminates. User response: Provide BMC Software Customer Support with the joblog and any associated messages from this job and the SVOS address space. |
SVM4407I | VOLUME volser RECOVERED FROM CATALOG Explanation: This message will follow a SVM4000I ATTEMPTING SPACVOLA RECOVERY message. StopX37/II was able to recover a volume added to the catalog entry of a VSAM data set after the data set was allocated to your task. Generally, this recovery is seen for shared VSAM data sets using record-level-sharing (RLS) or block-level-sharing for data integrity. User response: No action is necessary. |
SVM4410S | SCAN FOR NEW ALLOCATION FAILED Explanation: The allocation component SPACVOLA dynamically allocated to another volume but could not locate the returned volume in the TIOT. User response: Contact BMC Software Customer Support. |
SVM4411S | NEW VOLSER NOT FOUND IN TIOT Explanation: The allocation component SPACVOLA dynamically allocated to another volume but could not locate the new UCB address in the TIOT UCB list. User response: Contact BMC Software Customer Support. |
SVM4420S | JFCB VOLSER COUNT EQUAL ZERO. SEVERE ERROR Explanation: The JFCB volser count has been reduced to zero. No further volume recovery will be attempted for this allocation. User response: Contact BMC Software Customer Support. |
SVM4440I | RECOVERY NOT ALLOWED FOR ABSTR ALLOCATIONS Explanation: The data set was allocated with an absolute track address. The allocation component will not recover this data set. User response: No action is necessary. |
SVM4441I | RECOVERY NOT ALLOWED FOR CONTIG ALLOCATIONS Explanation: The data set was allocated in a contiguous extent. The allocation component will not recover this data set. User response: None required. If you determine that the application can process a multivolume data set, you can add a SKIP statement for the CONTIG check in the appropriate SMMSYSxx member to allow SPACVOLA to recover the data set. Alternatively, you can add a NOCHECK=CONTIG keyword to the active RLST member for the SPACVOLA function to allow SPACVOLA to recover the data set. |
SVM4442I | RECOVERY NOT ALLOWED FOR VIO DEVICES Explanation: The data set was allocated on a VIO device. The allocation component will not recover this data set. User response: No action is necessary. |
SVM4443I | RECOVERY NOT ALLOWED FOR IEHMOVE Explanation: The allocation component cannot recover data sets being processed by IEHMOVE. User response: No action is necessary. |
SVM445AI | CURRENT VOLUME NOT RESIDENT OR RESERVED Explanation: The data set resides on a volume that is not permanently resident or reserved. The allocation component cannot perform SPACVOLA processing for this data set. User response: No action is necessary. |
SVM445BI | PASSED DATA SET USING VOL=REF=DSNAME Explanation: The data set was passed from another job step and uses a volume referback to another data set. The allocation component cannot perform SPACVOLA processing for this data set. User response: No action is necessary. |
SVM445CI | SPACVOLA NOT ALLOWED. REASON = x Explanation: The message provides one of the following reasons:
User response: No action is necessary. |
SVM4450I | SPACVOLA ALLOWED ONLY ON SEQUENTIAL DATA SETS Explanation: SPACVOLA processing can only be performed on sequential or VSAM data sets. User response: No action is necessary. |
SVM4451I | RECOVERY TERMINATED: DATA SET IS NOT BEING PROCESSED SEQUENTIALLY Explanation: The allocation component could not make the data set multivolume because the data set organization was not physical sequential. User response: No action is necessary. |
SVM4452I | RECOVERY TERMINATED: DATA SET BEING PROCESSED BY EXCP Explanation: The allocation component (or StopX37/II) could not make the data set multivolume because the data set was being processed using EXCP. The allocation component cannot assume that the application can handle multivolume data sets. User response: If the data set is IAM format, contact BMC Customer Support. Otherwise, no action is required unless the application can process a multivolume data set. In that case, add a SKIP statement for the EXCP check in the appropriate SMMSYSxx member to allow SPACVOLA to recover the data set. Alternatively, you can add a NOCHECK=EXCP keyword to the active RLST member for the SPACVOLA function to allow SPACVOLA to recover the data set. |
SVM4453I | RECOVERY TERMINATED: DATA SET BEING PROCESSED USING NOTE/POINT LOGIC Explanation: The allocation component could not make the data set multivolume because the data set was being processed using NOTE/POINT logic. The allocation component cannot assume that the application can handle multivolume data sets. User response: None required. If you determine that the application can process a multivolume data set, you can add a SKIP statement for the NOTE check in the appropriate SMMSYSxx member to allow SPACVOLA to recover the data set. Alternatively, you can add a NOCHECK=NOTE keyword to the active RLST member for the SPACVOLA function to allow SPACVOLA to recover the data set. You can use the NOCHECK=NOTE to bypass this check for DB2 log data sets because they can be multivolume. |
SVM4454I | RECOVERY TERMINATED. VOLUME NOT ADDED. DISP=(NEW/MOD,KEEP) Explanation: This error condition applies only to non-SMS managed data sets. The SPACVOLA function could not add a volume to a data set whose disposition was either (NEW,KEEP) or (MOD,KEEP). Had SPACVOLA been allowed to add a volume, the added volume would not have been cataloged. Thus, subsequent job steps in the same job, plus any other jobs running at a later time would not know about the additional volume. User response: None required. If you determine that subsequent steps in the same job, plus any other jobs running at a later time, do not need to know about the added volume, you can add a SKIP statement for the DISP check in the appropriate SMMSYSxx member to allow SPACVOLA to recover the data set. Alternatively, you can add a NOCHECK=DISP keyword to the active RLST member for the SPACVOLA function to allow SPACVOLA to recover the data set. Bypassing the DISP check is not recommended. |
SVM4455I | RECOVERY TERMINATED: PERMANENT DATA SET REACHED WITHOUT CATALOG. DISP=(SHR/OLD/MOD) Explanation: This error condition applies only to non-SMS managed data sets. The SPACVOLA function could not add a volume to an existing data set (DISP=NEW not coded) because the catalog was not referenced due to the presence of VOL=SER in the JCL. Had SPACVOLA been allowed to add a volume, the added volume would not have been cataloged. Thus, subsequent job steps in the same job, plus any other jobs running at a later time would not know about the additional volume. Dynamic allocation of a data set that had been allocated earlier in the same step can also be a cause of this error. A specific example follows: A data set is allocated in JCL with DISP=NEW. Later, dynamic allocation is performed on the same data set with a disposition other than NEW. The data set is then written to using the second allocation. When SPACVOLA gets invoked, it sees the allocation control blocks associated with the second allocation and therefore sees a data set that is not cataloged and whose disposition is not NEW. User response: None required. If you determine that subsequent steps in the same job, plus any other jobs running at a later time, do not need to know about the added volume, you can add a SKIP statement for the DISP check in the appropriate SMMSYSxx member to allow SPACVOLA to recover the data set. Alternatively, you can add a NOCHECK=DISP keyword to the active RLST member for the SPACVOLA function to allow SPACVOLA to recover the data set. Bypassing the DISP check is not recommended. |
SVM4456I | RECOVERY TERMINATED: DATA SET IS ON MASS STORAGE VOLUME Explanation: The allocation component cannot perform SPACVOLA processing on data sets that are on MSS devices. User response: No action is necessary. |
SVM4458I | AUTOMATIC RESTART CODED Explanation: The allocation component cannot perform SPACVOLA processing on data sets that use automatic restart processing. User response: No action is necessary. |
SVM4459I | DATA SET PART OF CONCATENATION Explanation: The DD statement concatenates data sets. The allocation component cannot perform SPACVOLA processing on data sets that are concatenated. User response: No action is necessary. |
SVM4460I | RECOVERY TERMINATED: TWO DDNAMES REFERENCING SAME DATA SET Explanation: The allocation component could not make the data set multivolume because the data set was being referenced by two DD names. If SPACVOLA processing added another volume, the JFCB for the other DD would not contain the new volume. If this data set is a VSAM data set, StopX37/II was unable to add a volume because global parameter SHARED_VSAM is set to NO. User response: If you determine that the application can process a multivolume data set, you can add a SKIP statement for the DSNAME check in the appropriate SMMSYSxx member to allow SPACVOLA to recover the data set. Alternatively, you can add a NOCHECK=DSNAME keyword to the active RLST member for the SPACVOLA function to allow SPACVOLA to recover the data set. For VSAM data sets, setting global SHARED_VSAM=YES in active SMMSYSxx member will permit StopX37/II to perform SPACVOLA for all VSAM data sets being shared. |
SVM4461I | DATA SET/SPECIFIC REQUEST USED IN ANOTHER STEP Explanation: The allocation component could not make the data set multivolume because the same data set was referenced in another job step with a volume serial coded in the JCL (VOL=SER=). If SPACVOLA processing added another volume, the new volume would not be picked up by the later step. User response: No action is necessary. |
SVM4462I | DATA SET/VOL=REF REQUEST USED IN ANOTHER STEP Explanation: The allocation component could not make the data set multivolume because the same data set was referenced in another job step with a volume referback in the JCL (VOL=REF=). If SPACVOLA processing added another volume, the new volume would not be picked up by the later step. User response: No action is required. |
SVM4463I | DATA SET IS ALLOCATED TO ANOTHER JOB Explanation: The allocation component could not make the data set multivolume because the same permanent data set is referenced by another job that is running. If SPACVOLA processing added another volume, the new volume would not be picked up by the other job. User response: If you determine that the application can process a multivolume data set, you can add a SKIP statement for the ENQ check in the appropriate SMMSYSxx member to allow SPACVOLA to recover the data set. Alternatively, you can add a NOCHECK=ENQ keyword to the active RLST member for the SPACVOLA function to allow SPACVOLA to recover the data set. |
SVM4464I | RECOVERY TERMINATED: GLOBAL SHARED_VSAM=NO AND VSAM DATA SET IS ALLOCATED TO ANOTHER JOB Explanation: StopX37/II could not add a volume to a VSAM data set because it is referenced by another job and global parameter SHARED_VSAM is set to NO in active SMMSYSxx member. User response: Setting global parameter SHARED_VSAM=YES in the active SMMSYSxx allows StopX37/II to perform the SPACVOLA. Alternatively, a NOCHECK=ENQ keyword can be added to the active SPACVOLA RLST member to allow SPACVOLA to recover the data set. |
SVM4469W | storeGroup STORAGE GROUP IS DISABLED, RECOVERY TERMINATED Explanation: StopX37/II could not add a volume to a SMS-managed data set because DFSMS storage group storeGroup is either in DISNEW or DISALL status. The SPACVOLA recovery is terminated. User response: Change the status of the DFSMS storage group to enable use of pooled volumes. Refer to the IBM DFSMS Storage Administration Reference Manual for further information on DFSMS storage group status. |
SVM4470I | NO MORE VOLUMES IN STORAGE GROUP Explanation: During SPACVOLA processing, StopX37/II determined that there were no more eligible volumes in the storage group to switch to. User response: No action is necessary. |
SVM448AE | KEYWORD CANNOT START IN COLUMN 1. SEVERE ERROR. REORGANIZE TERMINATED. Explanation: DFDSS control cards cannot start in column 1. The user has placed an X37REORG keyword in column 1, which is invalid. User response: Review the X37REORG utility documentation (X37REORG is documented in the SPACVOLA function) and correct the appropriate keywords in your copy program control cards. |
SVM448BE | POOL pppppppppppppppppppppppppppppp NOT FOUND SEVERE ERROR. REORGANIZE TERMINATED. Explanation: The pool specified in the REORG-NSMS keyword in the SPACVOLA RLST does not exist. The pool name specified must be a valid pool. User response: Review the X37REORG utility documentation (X37REORG is documented in the SPACVOLA function) and correct the appropriate keywords in your copy program control cards. |
SVM448CE | GETMAIN FAILED FOR UCB LIST. SEVERE ERROR. REORGANIZE TERMINATED. Explanation: When X37REORG attempted to obtain storage for the UCB list control block the attempt failed. User response: Increase the region size on the X37REORG step and retry the job. |
SVM448DE | LINE WITH KEYWORD MUST HAVE TRAILING COMMA/BLANK/NULL. REORGANIZE TERMINATED. Explanation: Any copy control card statements that contain an X37REORG substitution keyword must be followed at some point on the line with a comma, blank, or null to terminate the parameter/subparameter in which that keyword is found. User response: Review the X37REORG utility documentation (X37REORG is documented in the SPACVOLA function) and correct the appropriate keywords in your copy program control cards. |
SVM448EE | THE OVOL KEYWORD MUST BE PRECEDED BY A COMMA OR LEFT PARENTHESIS. REORGANIZE TERMINATED. Explanation: The %OVOL X37REORG substitution keyword must be immediately preceded by a comma or a left parenthesis to indicate where the prior parameter/subparameter is delimited. User response: Review the X37REORG utility documentation (X37REORG is documented in the SPACVOLA function) and correct the appropriate keywords in your copy program control cards. |
SVM448FE | THE OVOL KEYWORD MUST BE TRAILED BY A COMMA OR RIGHT PARENTHESIS. REORGANIZE TERMINATED. Explanation: The %OVOL X37REORG substitution keyword must be immediately followed by a comma or a right parenthesis to indicate where the subsequent parameter/subparameter is delimited. User response: Review the X37REORG utility documentation (X37REORG is documented in the SPACVOLA function) and correct the appropriate keywords in your copy program control cards. |
SVM448GE | nnn RECORDS WERE READ AND PROCESSED FROM PARMLIB MEMBER mmmmmmmm. GOOD COMPLETION. Explanation: nnn records were read by X37REORG from the mmmmmmmm member in the parmlib library. Each record was successfully processed and X37REORG terminated successfully. User response: No action is necessary. |
SVM4480E | NO PARMS PASSED TO REORGANIZE PROCESSOR. SEVERE ERROR. REORGANIZE TERMINATED. Explanation: There were no parameters on the EXEC JCL card for program X37REORG. Several parameters are required. User response: Review the X37REORG utility documentation (X37REORG is documented in the SPACVOLA function) and add the appropriate parameter fields to your X37REORG Started Task JCL. |
SVM4481E | NO DSN PARM OR INVALID DSN. SEVERE ERROR. REORGANIZE TERMINATED. Explanation: There was not a DSN parameter or the DSN specified on the EXEC JCL card for program X37REORG was not a valid data set name. The DSN parameter is required and it must specify a valid z/OS data set name. User response: Review the X37REORG utility documentation (X37REORG is documented in the SPACVOLA function) and correct the appropriate parameter fields to your X37REORG Started Task JCL. |
SVM4482E | INVALID IVOL PARM. SEVERE ERROR. REORGANIZE TERMINATED. Explanation: The IVOL parameter specified on the EXEC JCL card for program X37REORG was not a valid volume name. The IVOL parameter must specify a valid z/OS volume ID. User response: Review the X37REORG utility documentation (X37REORG is documented in the SPACVOLA function) and correct the appropriate parameter fields to your X37REORG Started Task JCL. |
SVM4483E | NO MEM PARM OR INVALID MEM. SEVERE ERROR. REORGANIZE TERMINATED. Explanation: There was not a MEM parameter or the DSN specified on the EXEC JCL card for program X37REORG was not a valid member name. The MEM parameter is required and it must specify a valid z/OS partitioned data set member name. User response: Review the X37REORG utility documentation (X37REORG is documented in the SPACVOLA function) and correct the appropriate parameter fields to your X37REORG Started Task JCL. |
SVM4484E | NO POOL PARM OR INVALID POOL. SEVERE ERROR. REORGANIZE TERMINATED. Explanation: There was not a POOL parameter or the POOL specified on the EXEC JCL card for program X37REORG was not a valid pool name. The POOL parameter is required and it must specify a valid pool name. User response: Review the X37REORG utility documentation (X37REORG is documented in the SPACVOLA function) and correct the appropriate parameter fields to your X37REORG Started Task JCL. |
SVM4485E | NO STORCLAS PARM OR INVALID STORCLAS. SEVERE ERROR. REORGANIZE TERMINATED. Explanation: There was not a STORCLAS parameter or the STORCLAS specified on the EXEC JCL card for program X37REORG was not a valid SMS storage class name. The STORCLAS parameter is required and it must specify a valid SMS storage class name. User response: Review the X37REORG utility documentation (X37REORG is documented in the SPACVOLA function) and correct the appropriate parameter fields to your X37REORG Started Task JCL. |
SVM4486E | NO COPYTYPE PARM OR INVALID COPYTYPE. SEVERE ERROR. REORGANIZE TERMINATED. Explanation: There was not a COPYTYPE parameter or the COPYTYPE specified on the EXEC JCL card for program X37REORG was not a valid copy type. Currently the only two valid COPYTYPE values are DSS (DFDSS copy type) or FDR (FDR copy type). User response: Review the X37REORG utility documentation (X37REORG is documented in the SPACVOLA function) and correct the appropriate parameter fields to your X37REORG Started Task JCL. |
SVM4487E | NEITHER POOL= NOR STORCLAS= WAS FOUND IN PARMS. SEVERE ERROR. REORGANIZE TERMINATED. Explanation: There was neither a POOL parameter nor a STORCLAS parameter specified on the EXEC JCL card for program X37REORG. One or both of these parameters must be specified. User response: Review the X37REORG utility documentation (X37REORG is documented in the SPACVOLA function) and correct the appropriate parameter fields to your X37REORG Started Task JCL. |
SVM4488E | INVALID PARM FOUND IN THE INPUT PARM STRING. SEVERE ERROR. REORGANIZE TERMINATED. Explanation: There was an invalid parameter specified on the EXEC JCL card for program X37REORG. User response: Review the X37REORG utility documentation (X37REORG is documented in the SPACVOLA function) and correct the appropriate parameter fields to your X37REORG Started Task JCL. |
SVM4490I | SPACSWIR REDUCED INITIAL ALLOC ON CANDIDATE VOLUME DOWN TO MAX ALLOWED. Explanation: A data set extended to a new (candidate) volume. However, the secondary value that was specified in the JCL (which is used for the first allocation made on the new volume), exceeds the maximum value that is allowed for this data set type, which is 65,535 tracks. SPACSWIR reduces the secondary value to either 4369 cylinders or 65,535 tracks, depending on whether the original allocation was in cylinders or tracks. This message should be followed by the SVM4801I message to indicate the reduced secondary amount. User response: No action is necessary. |
SVM4491I | DATA SET HAS REACHED MAXIMUM SPACE ALLOWED ON VOLUME (65,535 TRKS) Explanation: SPACSECR was unable to reduce the secondary amount a sequential data set defined without extended attributes because it already occupied the maximum space allowed on a volume (65,535 TRKS). will attempt SPACVOLA for the data set. User response: No action is necessary. |
SVM4500I | RECOVERY TERMINATED: NO VOLUMES AVAILABLE FOR SPACVOLA Explanation: The allocation component could not perform SPACVOLA processing because none of the volumes provided in the SPACVOLA RLST VOLSER list had the correct unit type, or the secondary space allocation would not fit in one extent on any eligible volume in the VOLSER list. User response: Making the job/dsn eligible for SPACSECR or SPACSWIR processing or both in the appropriate FLST/RLSTs could alleviate this problem. |
SVM4501I | NOT ENOUGH SPACE ON VOLUME volume Explanation: The VOLSER list found in the SPACVOLA RLST did not provide an eligible volume with enough space for the secondary space amount to fit in one extent; however, because OPER=YES was also specified in the SPACVOLA RLST, the operator was prompted to select a volume, but the volume selected also did not contain enough space for the secondary to be obtained in one extent. If the operator is providing the candidate volumes, the operator will be prompted for another volume. User response: No action is necessary. |
SVM4502I | VOLUME volume NOT WITHIN DEVICE GROUP Explanation: The VOLSER list found in the SPACVOLA RLST did not provide an eligible volume with enough space for the secondary space amount to fit in one extent; however, because OPER=YES was also specified in the SPACVOLA RLST, the operator was prompted to select a volume, but the volume selected was not found the same generic group. This message will also be issued if the user has FLST/RLST tracing turned on. In that case the message will appear once for every volume in the VOLSER list that is not found in the same generic group. User response: If the operator is providing the candidate volumes, the operator will be prompted for another volume. |
SVM4503I | ENTER SPACVOLA OPTION FOR DSN=dsn, VOLSER=volser Explanation: The VOLSER list found in the SPACVOLA RLST did not provide an eligible volume with enough space for the secondary space amount to fit in one extent; however, because OPER=YES was also specified in the SPACVOLA RLST, the operator is being prompted by this message to supply a volume for SPACVOLA processing. User response: If the operator responds with a volume name, the allocation component will determine if the volume can be used. If the volume cannot be used, the operator will be prompted for another volume. The operator can also wait for more disk space to be available on one or more of the volumes in the SPACVOLA RLST VOLSER list and reply retry, which will cause the allocation component to retry all of the volumes in the VOLSER list looking for an eligible one with enough space. If the operator replies ignore, the process terminates the recovery and the job will fail. |
SVM4506S | BAD RETURN CODE FROM UNIT VERIFICATION ROUTINE Explanation: The allocation component received an unexpected return code from the unit verification routine while trying to obtain the UCB list. User response: Contact BMC Software Customer Support. |
SVM451AI | VOLUME volume REJECTED BY DADSM EXIT Explanation: The VOLSER list found in the SPACVOLA RLST did not provide an eligible volume with enough space for the secondary space amount to fit in one extent; however, because OPER=YES was also specified, the operator was prompted to select a volume for SPACVOLA processing; however, the volume provided was rejected by the installation's DADSM exit. If the operator is providing the candidate volumes, the operator will be prompted for another volume. User response: No action is necessary. |
SVM451BI | VOLUME volume REJECTED BY VOLSER EXIT Explanation: The VOLSER list found in the SPACVOLA RLST did not provide an eligible volume with enough space for the secondary space amount to fit in one extent; however, because OPER=YES was also specified, the operator was prompted to select a volume for SPACVOLA processing; however, the volume provided was rejected by the installation's VOLSER exit. User response: If the operator is providing the candidate volumes, the operator will be prompted for another volume. |
SVM4510I | VOLUME volume IS RESERVED Explanation: The specified volume is held by some other job. User response: No action is necessary. |
SVM4518I | DATA SET ALREADY EXISTS ON VOLUME volume Explanation: The VOLSER list found in the SPACVOLA RLST did not provide an eligible volume with enough space for the secondary space amount to fit in one extent; however, because OPER=YES was also specified, the operator was prompted to select a volume for SPACVOLA processing; however, the volume provided already has a data set on it with the same name as the data set being recovered. User response: If the operator is providing the candidate volumes, the operator will be prompted for another volume. |
SVM4519I | RECOVERY TERMINATED: DADSM EXIT REJECTED REQUEST Explanation: The allocation component could not make the data set multivolume because the installation's DADSM exit (IGGPRE00) would reject the allocation on the new volume. User response: The installation's DADSM exit could be modified to allow the allocation on the new volume. Contact BMC Software Customer Support. |
SVM4520I | DATA SET ALREADY USES VOLUME volume Explanation: The VOLSER list found in the SPACVOLA RLST did not provide an eligible volume with enough space for the secondary space amount to fit in one extent; however, because OPER=YES was also specified, the operator was prompted to select a volume for SPACVOLA processing; however, the volume provided has already been used by the data set being recovered. If the operator is providing the candidate volumes, the operator will be prompted for another volume. User response: No action is necessary. |
SVM4521S | GETMAIN FAILED FOR CATALOG WORK AREA Explanation: The allocation component could not obtain storage for internal work areas. Control was returned to VSAM. User response: The abending job was extremely short on virtual storage. The REGION parameter should probably be increased. |
SVM4522S | LOCATE FAILED FOR DSN dsn (RC=returnCode - reasonCode) Explanation: During SPACVOLA processing for a VSAM file, the allocation component issued a LOCATE to obtain the current volume list that the data set resides on, but the LOCATE request failed. The recovery is terminated. User response: The LOCATE return and reason codes are provided in the message. Contact BMC Software Customer Support and have the return and reason codes available. |
SVM4523S | NO VOLUMES RETURNED BY LOCATE Explanation: During SPACVOLA processing for a VSAM file, the allocation component issued a LOCATE to obtain the current volume list that the data set resides on; the LOCATE request was successful but returned an empty volume list. The recovery is terminated. User response: Contact BMC Software Customer Support. |
SVM4575S | GETMAIN FOR UNIT VERIFICATION ROUTINE FAILED Explanation: The allocation component could not obtain storage for the UCB list. User response: The abending job was extremely short on virtual storage. The REGION parameter should probably be increased. |
SVM4576S | EDTINFO MACRO FAILURE FOR UNIT=xxxxxxxx. RC=nn RS=nn Explanation: StopX37/II encountered unexpected return (RC=) and reason (RS=) codes when obtaining the UCB list for a specified unit (UNIT=), causing the SPACVOLA process to fail. User response: Report this error message to BMC Software Customer Support. You might be able to work around the error by doing one of the following actions:
Example: SET SPACVOLA=5 VOLSER=(VOL001,VOL002) UNIT=3390
|
SVM458CS | VOLUME volume WAS NOT IN RLST VOLSER LIST Explanation: The VOLSER list found in the SPACVOLA RLST provides a volume list to use to pick a volume to add during SPACVOLA processing. When FLST/RLST tracing is active, this message will appear once for every volume in the generic group that is not also in the VOLSER list. User response: No action is necessary. |
SVM458DS | SVOLUME volume DID NOT HAVE CORRECT MOUNT TYPE TO MATCH THE MNTYPE SPECIFICATION Explanation: The volume was not used by SPACVOLA because the mount type did not match the MNTYPE setting on the SPACVOLA RLST SET statement. User response: No action is necessary. |
SVM4581S | VOLUME volume IS NOT CORRECT DEVICE TYPE Explanation: The VOLSER list found in the SPACVOLA RLST did not provide an eligible volume with enough space for the secondary space amount to fit in one extent; because OPER=YES was also specified, the operator was prompted to select a volume for SPACVOLA processing; however, the volume provided was not of a similar device type. User response: If the operator is providing the candidate volumes, the operator will be prompted for another volume. |
SVM4582S | VOLUME volume IS CONTROLLED BY JES3 Explanation: The VOLSER list found in the SPACVOLA RLST did not provide an eligible volume with enough space for the secondary space amount to fit in one extent; because OPER=YES was also specified, the operator was prompted to select a volume for SPACVOLA processing; however, the volume provided is controlled by JES3. User response: If the operator is providing the candidate volumes, the operator will be prompted for another volume. |
SVM4583S | VOLUME volume NOT RESERVED OR PERMANENTLY RESIDENT Explanation: The VOLSER list found in the SPACVOLA RLST did not provide an eligible volume with enough space for the secondary space amount to fit in one extent; because OPER=YES was also specified, the operator was prompted to select a volume for SPACVOLA processing; however, the volume provided is not reserved or permanently resident. User response: If the operator is providing the candidate volumes, the operator will be prompted for another volume. |
SVM4584S | VOLUME volume NOT ONLINE Explanation: The VOLSER list found in the SPACVOLA RLST did not provide an eligible volume with enough space for the secondary space amount to fit in one extent; because OPER=YES was also specified, the operator was prompted to select a volume for SPACVOLA processing; however, the volume provided is not currently online. User response: If the operator is providing the candidate volumes, the operator will be prompted for another volume. |
SVM4585S | VOLUME volume IS CHANGING STATUS Explanation: The VOLSER list found in the SPACVOLA RLST did not provide an eligible volume with enough space for the secondary space amount to fit in one extent; because OPER=YES was also specified, the operator was prompted to select a volume for SPACVOLA processing; however, the volume provided is currently changing status; probably waiting to go offline. User response: If the operator is providing the candidate volumes, the operator will be prompted for another volume. |
SVM4586S | VOLUME volume IS SMS MANAGED Explanation: The VOLSER list found in the SPACVOLA RLST did not provide an eligible volume with enough space for the secondary space amount to fit in one extent; because OPER=YES was also specified, the operator was prompted to select a volume for SPACVOLA processing; however, the volume provided is SMS managed and the data set currently resides on a non-SMS volumes. User response: If the operator is providing the candidate volumes, the operator will be prompted for another volume. |
SVM4587S | VOLUME volume HAS WRONG DEVICE CHARACTERISTICS Explanation: The VOLSER list found in the SPACVOLA RLST did not provide an eligible volume with enough space for the secondary space amount to fit in one extent; because OPER=YES was also specified, the operator was prompted to select a volume for SPACVOLA processing; however, the volume provided has different device characteristics than the volumes on which the data set already resides. This situration is usually because the data set is already on a cached device and the selected device is not cached. The reverse situation will cause the same message to appear. User response: If the operator is providing the candidate volumes, the operator will be prompted for another volume. If you determine that it is acceptable to add volumes with different device characteristics, you can add a SKIP statement with the DC option in SMMSYSxx to bypass this check or add the NOCHECK=DC operand to the SPACVOLA RLST. |
SVM4600S | ALLOCATION FAILED FOR volid, R15=r15, ERROR RC=returnCode, INFORMATION RC=returnCode Explanation: The allocation component was attempting to dynamically allocate to another volume (volid), but the DYNALLOC SVC failed. For further information consult SPL: SUPERVISOR SERVICES MACROS. User response: Contact BMC Software Customer Support. |
SVM4601I | RECOVERY TERMINATED: DATA SET EXISTS ON MAXIMUM VOLUMES Explanation: The allocation component uses the MAXVOL keyword found in SMMSYSxx (global) or the SPACVOLA operand in the SPACVOLA RLST (local) to determine how many volumes the data set can reside on. In this case the data set already resides on the maximum number of volumes specified in one of these places. User response: If more volumes are required, increase the MAXVOL or SPACVOLA operand and rerun the job. |
SVM4602E | EXCEEDED RETRY LIMIT ON ENQUEUE OF SYSZTIOT RESOURCE - SPACVOLA FAILS. Explanation: Another task within the address space had enqueue on the SYSZTIOT resource, preventing SPACVOLA from continuing. SPACVOLA will attempt to obtain the SYSZTIOT resource after a one-second wait, allowing the other task to release the resource. SPACVOLA will attempt to retry the enqueue up to twenty seconds before failing. User response: This problem is typically seen when using a program that invokes SPACVOLA under multiple TCBs (such as a utility program used to REORG multiple VSAM data sets). The problem is usually corrected by rerunning the job. If the problem persists, you can try one or more of the following:
|
SVM4603E | UNEXPECTED ERROR DURING ENQUEUE OF SYSZTIOT RESOURCE - SPACVOLA FAILS. Explanation: An unexpected error occurred when performing enqueue of SYSZTIOT resource. SPACVOLA fails. User response: Issue F SVOSJOB,SVOS T,MSGID,DMP console command to capture a dump next time this message is issued. Contact BMC Software support and send in the dump. (Issue F SVOSJOB,SVOS T,MSGID,NDMP console command to reverse this setting and allow this message to display without capturing a dump.) |
SVM4604E | EOV INVOKED FOR A NON-VSAM DATA SET DURING CLOSE - SPACVOLA FAILS Explanation: A request for more space (EOV processing) was made for a non-VSAM data set while the data set was being CLOSED. SPACVOLA was unable to acquire exclusive control of the SYSZTIOT resource and failed. This message requires the following 'perfect storm' scenario:
User response: This is a very unusual problem and typically seen when using a program that invokes SPACVOLA under multiple TCBs (such as a utility program used to REORG multiple VSAM data sets). The problem is usually corrected by rerunning the job. If the problem persists, you can try one or more of the following:
|
SVM4700S | SCAN FOR NEW ALLOCATION FAILED Explanation: The allocation component dynamically allocated to another volume but could not locate the returned DDNAME in the TIOT. User response: Contact BMC Software Customer Support. |
SVM4701S | GETMAIN FOR NEW VDT FAILED Explanation: During SPACVOLA processing, a GETMAIN failed attempting to build a new VDT control block. User response: Try rerunning the job with a larger region size. If that also fails, contact BMC Software Customer Support. |
SVM4801I | REDUCED SPACE FROM orgaunits TO newa Explanation: The allocation component has reduced the secondary space allocation from the original allocation (orga) to the largest extent on the volume (newa). The allocation was requested in units of CYL, TRK, BLK, MAV, KAV, or AVG (units).The secondary space allocation has not been permanently changed. User response: No action is necessary. |
SVM4802I | NO AVAILABLE VOLUMES IN STORAGE GROUP Explanation: This message can be issued when attempting to allocate another volume to an existing SMS data set, or when allocating a new SMS data set. If allocating to an existing SMS data set: The secondary space request exceeded the available space on the remaining volumes in the storage group and any extended storage group(s). The SPACSWIR function was either not active for the data set, or the available space went below the SPACSWIR floor limit. If allocating a new SMS data set: There were no volumes available in the storage group(s) for the allocation. User response: If the message is displayed for an existing SMS data set: Activate the SPACSWIR function in and set the SPACSWIR floor percentage to fit on the available space in the storage group. Using a SPACSWIR floor setting of 0 is recommended. If the message is displayed for a new SMS data set: Make sure the volumes in the storage group(s) are enabled and online for new allocations. Users of the SMSSELCT function in the BMC AMI Storage Allocationproduct might also need to check if the data set qualifies for pooling in SMSSELCT. When specifying pools for a new SMS allocation with SMSSELCT, you should ensure there are pool volumes that also reside in the available storage group(s) for the allocation. Otherwise, the SMS allocation will fail. |
SVM4804W | MULTI STRIPE DATA SET CANNOT SWITCH AND HAS 123 EXTENTS Explanation: The multistripe data set that is being recovered has already used the maximum 123 extents, and z/OS cannot process an additional volume that is dynamically added to a multistriped data set. The recovery is terminated. User response: No action is necessary. |
SVM4805W | TEMPORARY STRIPE DATA SET CANNOT SWITCH AND HAS 123 EXTENTS Explanation: The temporary striped data set that is being recovered has already used the maximum 123 extents, and z/OS cannot process an additional volume that is dynamically added to a temporary striped data set. The recovery is terminated. User response: No action is necessary. |
SVM4806W | VOLUME FULL AND MULTI STRIPE DATA SET CANNOT SWITCH Explanation: The multistripe data set that is being recovered is on a volume that is full, and z/OS cannot process an additional volume that is dynamically added to a multistripe data set. The recovery is terminated. User response: No action is necessary. |
SVM4807W | VOLUME FULL AND TEMPORARY STRIPE DATA SET CANNOT SWITCH Explanation: The temporary striped data set that is being recovered is on a volume that is full, and z/OS cannot process an additional volume that is dynamically added to a temporary striped data set. The recovery is terminated. User response: No action is necessary. |
SVM4808W | SECONDARY REDUCTION WENT TO 0 FOR MULTI STRIPE DATA SET Explanation: The allocation component attempted to reduce the secondary space amount for a multistripe data set, but the amount was reduced to zero before the allocation would fit on the volume, and z/OS cannot process an additional volume that is dynamically added to a temporary striped data set. The secondary reduction is performed by multiplying the original secondary space amount by the reduction percentage in the SPACSECR RLST. The recovery is terminated. User response: No action is necessary. |
SVM4809I | dsn REACHED MAX EXTENTS ON VOLSER volser Explanation: StopX37/II attempted to reduce the secondary space amount for a VSAM data set. The data set has reached the maximum number of allowable extents (123 for VSAM data sets) on an individual volume. User response: None. This message is for information only, which should be followed by the SVM4000I message when FLST/RLST rules permit. |
SVM4810I | CANNOT SPACVOLA dsnIDCAMS AND PSE COMPRESSED Explanation: During SPACVOLA processing, StopX37/II detected that IDCAMS REPRO was writing to a PSE Compressed data set. REPRO cannot tolerate volume adds when the output data set is PSE Compressed. Because data loss could occur if a volume was added, SPACVOLA processing is instead bypassed for the data set. User response: No action is necessary. |
SVM4811W | UNABLE TO PROVIDE ADDITIONAL CANDIDATE VOLUMES FOR A MULTISTRIPE VSAM DATA SET Explanation: StopX37/II was attempting to recover a NO SPACE condition with SPACVOLA for a multistripe VSAM data set and one of the following conditions occurred:
User response: Condition 1: Provide more available space in the DFSMS storage group. Condition 2: Increase the SPACVOLA maximum volume limit in the qualifying SPAVOLA RLST rule. Condition 3: Set MULTISTRIPE=YES in the SMMSYSxx BBPARM member and refresh the member. Condition 4: Apply the corrective fix for IBM APAR OA25909. |
SVM4812I | count DIRECTORY BLOCKS SUCCESSFULLY ADDED TO dsn Explanation: This message notes that the StopX37/II PDSDIRAD function successfully recovered a PDS that encountered a SB14 abend (directory out-of-space). count (which has a default of 1) notes the number of directory blocks added to the PDS. dsn notes the PDS that was recovered. Processing continues. User response: No action is necessary. |
SVM4813W | dsn DIRECTORY WAS NOT EXPANDED. RC=returnCode, RS=reasonCode, ERROR=errorDesc Explanation: This message notes that the StopX37/II PDSDIRAD function could not successfully recover a PDS that encountered an SB14 abend (directory out-of-space). dsn notes the PDS that could not be recovered. returnCode and reasonCode note the internal return and reason codes of the PDSDIRAD function process. errorDesc is a 50-byte description of the error. There are several environmental checks performed on the PDS that could prohibit recovery. These checks include:
Processing terminates.User response: If errorDesc is not one of the environmental message listed here, contact BMC Customer Support. |
SVM4814W | ERROR DETAIL: RC=xxxxxxxx RS=xxxxxxxx FDBK=xxxxxxxx mm........mm Explanation: This message follows SVM4813W and provides detailed information particularly in the case of an I/O error. The text information in this messages (mm........mm) may or may not be present. User response: See message SVM4813W. |
SVM4815I | MAINVIEW SRM DS SIZE ASSIST FEATURE IS NOT ACTIVE Explanation: SVALLOC issued a request to the DS Size Assist task, but the task is not active. Processing continues. User response: If the DS Size Assist feature should be active, review the JESLOG messages to determine why the task is not active. To restart the feature, start SVDSSIZE or recycle SVALLOC. |
SVM4816E | MAINVIEW SRM DS SIZE ASSIST FEATURE ENCOUNTERED AN ERROR IN THE MAINVIEW SRM ADDRESS SPACE Explanation: SVALLOC issued a request to the DS Size Assist task. The task encountered an error. Processing continues. User response: Review the JESLOG messages to determine the error. If the DS Size Assist feature disabled itself, you can restart it by issuing the SVDSSIZE command or by recycling SVALLOC. |
SVM4820E | Retrieval Error, see SVOS job log for error msgs
Explanation: Research related messages in the SVOS job log. User response: If the information is not self-explanatory contact BMC Customer Support. |
Data retrieval error, SVOS not active Explanation: Research related messages in the SVOS job log. User response: If the information is not self-explanatory contact BMC Customer Support. | |
SYSPRINT IN USE BY SVOS Explanation: The SRDF/A data retrieval process allocates SYSPRINT. Therefore, it cannot be in use by any other SVOS process at the time the ESRDFA view is invoked. It also cannot be hard coded in the SVOS PROC. This message will display if SYSPRINT is coded in the SVOS PROC, if a previous invocation of the ESRDFA view is still processing, or another SVOS process is using SYSPRINT. User response: If SYSPRINT is coded in the SVOS PROC, rename SYSPRINT to DISPRINT in the SVOS PROC and recycle SVOS. If it is not found in the SVOS PROC, SYSPRINT is in use by a previous invocation of ESRDFA, or by some other process in SVOS. In this instance, invoke the ESRDFA view at a later time. | |
EMC subsystem command character not found Explanation: The SRDF/A data retrieval process utilizes the EMC subsystem command characters. SVOS attempted to locate the command characters in the Subsystem Communications Vector Table but was unable to find the correct control block. Check if the started task that executes program EMCSTC is active. If not, start the task and retry the view. If it is active, enter the command character(s) defined in the PARMLIB member used by the EMCSTC program into the EMC_CMDPRFX= parameter in the SMMSYSxx member of the SVOS started task. Then refresh the SMMSYSxx member and retry the view. User response: If the problem persists, contact BMC Customer Support. | |
No EMC boxes found Explanation: In the process of displaying the view information EMC boxes could not be found. If EMC boxes are displayed in the Configuration view, then retry this view. If EMC boxes are not displayed in the Configuration view, then they are unavailable. User response: If the problem persists, contact BMC Customer Support. | |
Box @@@@@@@@@@@@ not found in EMC box table Explanation: The selected EMC box was not found the box table created by the data retrieval process. If the selected box is an EMC box and is displayed in the Configuration view, retry the view. User response: If the problem persists, contact BMC Customer Support. | |
No records Returned Explanation: The SRDFA command was executed against devices selected and no SRDF/A data was returned from the command. The SNAP DD output in the SVOS address space contains the SRDFA commands entered under the title SRDFA CMD TABLE. User response: If you believe the result of the command is in error contact BMC Customer Support. | |
UNABLE TO LOCATE REQUESTED SUBSYSTEM
Explanation: The EMC subsystem is either not active or the command characters used in the SRDFA command issued by SVOS are incorrect. Ensure the address space executing EMCSTC is running. If it is, compare the EMC_CMDPRFX parameter defined in the SVOS SMMSYSxx PARMLIB member with the EMC subsystem command characters displayed in the message "EMCIN03I EMC SUBSYSTEM USING COMMAND PREFIX" located in the EMC address space. If they do not match, update the EMC_CMDPRFX parameter, refresh the SMMSYSxx member and try the view again. User response: If you believe the result of the command is in error contact BMC Customer Support. | |
SVM4850I | SPACSECA PERCENTAGE SET TO ZERO IN RLST. RECOVERY FAILED Explanation: The percentage specified in the SPACSECA RLST is zero, so SPACSECA cannot process. The recovery is terminated. User response: For SPACSECA to process for this data set, set the SPACSECA percentage in the SPACSECA RLST to a nonzero value. |
SVM4851S | DEVTYPE SVC FAILED Explanation: The allocation component attempted to calculate the primary space allocation and received a bad return code from the DEVTYPE SVC. User response: Contact BMC Software Customer Support. |
SVM4852S | PRIMARY SPACE CALC: ALLOCATION NOT IN CYLINDERS, TRACKS, BLOCKS, OR AVGREC Explanation: The allocation component attempted to calculate the primary space allocation in terms of cylinders, tracks, or blocks. It could not confirm that the data set was allocated in any of these units. User response: Contact BMC Software Customer Support. |
SVM4853S | PRIMARY SPACE CALC: NO BLKSIZE FOUND IN JFCB Explanation: The allocation component attempted to calculate the primary space allocation. The data set was allocated with BLK, but the JFCB did not contain a block size. User response: Contact BMC Software Customer Support. |
SVM4854S | PRIMARY SPACE CALC: RECORD EXCEEDS TRACK SIZE Explanation: The allocation component attempted to calculate the primary space allocation. The data set was allocated with BLK, but the block size exceeded the track size. User response: Contact BMC Software Customer Support. |
SVM4855I | SET SECONDARY SPACE USING pct% OF PRIMARY(priaUnits):secaUnits Explanation: The allocation component provided a secondary space allocation (seca). The secondary space allocation is calculated from the percentage provided by the action statement (pct) times the primary space allocation (pria) in units CYL, TRK, or BLK (units). User response: No action is necessary. |
SVM4860S | RESERVE HELD. CANNOT ISSUE LSPACE. SPACSECB FAILED Explanation: A volume is held by another job. User response: Clear the reserve and rerun. |
SVM4861S | LSPACE FAILED. SPACSECB NOT COMPLETED Explanation: During SPACSECB processing, an LSPACE was issued to determine how much space was available on the volume. The LSPACE failed. SPACSECB processing is terminated. User response: Contact BMC Software Customer Support. |
SVM4862I | MAXIMUM SPACE ON VOLUME IS ZERO. CANNOT SPACSECB Explanation: SPACSECB processing determined that the volume the data set was on had no more space available on it. SPACSECB processing is terminated. User response: Make some space available on the volume and rerun the job. |
SVM4863S | TRKCALC FAILED. SPACSECB NOT COMPLETED Explanation: During SPACSECB processing, a TRKCALC was issued to determine how much space was available on the volume. The TRKCALC failed. SPACSECB processing is terminated. User response: Contact BMC Software Customer Support. |
SVM4864I | MAXIMUM SPACE ON VOLUME IS LESS THAN A CA. CANNOT SPACSECB Explanation: SPACSECB processing determined that the volume the data set was on did not have enough space for a single control area (CA). VSAM files cannot have an extent allocated less than a CA in size. The process is terminated. User response: Make more space available on the volume and rerun the job. |
SVM4865I | CHANGED SPACE FROM nnnnunits TO nnnn Explanation: SPACSECB processing changed the secondary space to the number listed in the message. The space units for the data set is also listed in the message. User response: No action is necessary. |
SVM4866I | SPACE NOT ALLOCATED IN CYLINDERS OR TRACKS. SPACSECB FAILED Explanation: SPACSECB processing can only modify space amounts that are allocated in tracks or cylinders. The data set being processed is in neither of these units. The process terminates. User response: Reallocate the data set in either tracks or cylinders and SPACSECB can process it. |
SVM4867S | AVERAGE BLOCK LENGTH NOT PROVIDED FOR DATA SET USING AVGREC Explanation: The average block length was not found in the JFCB for a data set using AVGREC. Typically, this situation can occur when another OEM product modifies the JFCB control block that will prevent from determining the proper allocation size during an extend. User response: Contact BMC Customer Support. |
SVM4868I | SPACSECB SPACE REQUEST WENT BELOW LIMIT Explanation: SPACSECB could not find an extent on the volume that was large enough to be over the SPACSECB floor limit. SPACSECB processing terminates. User response: No action is necessary. |
SVM4869S | STATUS MUST COMPLETE FAILED. SPACSECB NOT COMPLETED. Explanation: During SPACSECB processing, a STATUS command was issued to ensure access to the space available on the volume. The STATUS command failed. SPACSECB processing is terminated. User response: Contact BMC Software Customer Support. |
SVM4870S | RESERVE HELD. CANNOT ISSUE LSPACE. SPACSECI FAILED Explanation: A volume is held by another job. User response: Clear the reserve operation and rerun. |
SVM4871S | LSPACE FAILED. SPACSECI NOT COMPLETED Explanation: During SPACSECI processing an LSPACE was issued to determine how much space was available on the volume. The LSPACE failed. SPACSECI processing is terminated. User response: Contact BMC Software Customer Support. |
SVM4872I | MAXIMUM SPACE ON VOLUME IS ZERO. CANNOT SPACSECI Explanation: SPACSECI processing determined that the volume the data set was on had no more space available. SPACSECI processing is terminated. User response: Make some space available on the volume and rerun the job. |
SVM4873S | TRKCALC FAILED. SPACSECI NOT COMPLETED Explanation: During SPACSECI processing, a TRKCALC was issued to determine how much space was available on the volume. The TRKCALC failed. SPACSECI processing is terminated. User response: Contact BMC Software Customer Support. |
SVM4874I | increased/decreased SPACE FROM nnnn units TO nnnn Explanation: SPACSECI processing increased or decreased the secondary space to the value listed in the message. The allocation units for the data set are also listed in the message. User response: No action is necessary. |
SVM4875S | SMAVGREC PROCESSING FAILED. SPACSECI FAILED. Explanation: The AVGREC processor failed during SPACSECI processing causing SPACSECI to fail. User response: Contact BMC Software Customer Support. |
SVM4900S | DEVTYPE SVC FAILED Explanation: The allocation component attempted to calculate the largest contiguous extent on a volume in terms of blocks but received a bad return code from the DEVTYPE SVC. User response: Contact BMC Software Customer Support. |
SVM4901S | ALLOCATION NOT IN CYLINDERS, TRACKS, OR BLOCKS Explanation: The allocation component attempted to calculate the largest contiguous extent on a volume in terms of cylinders, tracks, or blocks. It could not confirm that the data set was allocated in any of these units. User response: Contact BMC Software Customer Support. |
SVM4902S | BLKSIZE NOT FOUND IN JFCB Explanation: The allocation component attempted to calculate the largest contiguous extent on a volume in terms of blocks. The data set was allocated with BLK, but the JFCB did not contain a block size. User response: Contact BMC Software Customer Support. |
SVM4903S | DATA SET ALLOCATED IN BLOCKS WHICH EXCEED TRACK SIZE Explanation: The allocation component attempted to calculate the largest contiguous extent on a volume in terms of blocks. The data set was allocated with BLK, but the block size exceeded the track size. User response: Contact BMC Software Customer Support. |
SVM4904E | LSPACE SVC FAILED Explanation: The allocation component issued an LSPACE SVC to obtain the space information for a volume. The LSPACE failed. If SPACSECB is processing, the recovery is terminated. If SPACVOLA is processing, SPACVOLA will use the next volume in the VOLSER list/POOL. User response: Contact BMC Software Customer Support. |
SVM4905S | OBTAIN FAILED FOR DSN=dsn VOL=volume RC=returnCode Explanation: When the system was attempting to obtain another extent for the data set, the allocation component tried to read the DSCB information from the VTOC. The request failed. User response: Contact BMC Software Customer Support. |
SVM4906S | NO FREE DSCBS ON VOLUME volume Explanation: The VOLSER list found in the SPACVOLA RLST did not provide an eligible volume with enough space for the secondary space amount to fit in one extent; however, because OPER=YES was also specified, the operator was prompted to select a volume for SPACVOLA processing; however, the volume provided has no more DSCBs and cannot be used. This message will also be issued if the user has FLST/RLST tracing turned on. In that case the message will appear once for every volume in the VOLSER list that has no more DSCBs. User response: No action is necessary. |
SVM4921S | SMS VOLUMES IN STORAGE GROUP ARE FULL Explanation: While attempting to add a volume for a data set, there was insufficient space on any volume in the storage group to allow the SMS VSAM data set to extend. SPACSWIR processing is terminated. User response: Reducing the SPACSWIR floor percentage for the data set may allow the new extent to fit on another storage group volume. Otherwise, free up space within the storage group to allow the data set to extend. |
SVM4922S | EXTENT WILL EXCEED THE 4GB LIMIT Explanation: This message indicates a new extent will cause a VSAM data set to exceed the 4GB limit. SPACSWIR processing is terminated. User response: Reducing the SPACSWIR floor percentage for the data set may allow the new extent to fit within the 4GB limit. Otherwise, verify if the VSAM data set requires reorganization to allow the data set to extend. |