This section details messages generated during processing by the Parallel Development Manager (PDM) when you are using the CA Endevor SCM Parallel Development option. Possible causes and corrective actions to take in error situations are provided.
Reason:
The PDM installation password is missing or invalid. Either PDM was installed incorrectly or the PDM license has expired.
Action:
Verify that the correct PDM password is specified in the installation C1DEFLTS table. Reassemble the table if necessary.
Reason:
PDM was unable to obtain virtual storage to perform the requested function. The region size associated with the batch job or TSO session is not large enough for PDM to complete the current operation.
Action:
If the error occurred during batch execution of PDM, increase the REGION parameter in the JOB or EXEC JCL statement. If the error occurred during foreground execution, logon with a larger region size.
Reason:
The specified member exists in the specified data set and the REPLACE option was not used in the BUILD WIP or the MERGE statement. PDM will terminate the Build WIP or Merge processing.
Action:
If you want to replace the specified member, add the REPLACE clause to the BUILD WIP or MERGE statement or the appropriate member/Element mask. Alternatively, you can delete the member from the specified data set.
Reason:
The Merge processing routine was called with an incorrect internal control block structure. PDM will terminate Merge processing.
Action:
Retry the Merge operation. If the problem persists, contact your administrator.
Reason:
The Merge operation detected a WIP record with an invalid prefix. PDM is unable to determine what to do with the record. The record in error will be printed in message PDM0026E. PDM will terminate the Merge process.
Action:
See message PDM0026E to identify the WIP record that is in error. Use the PDM Edit WIP function to edit the WIP file and correct the WIP record. After the WIP file has been corrected, resubmit the Merge request.
Reason:
This message follows message PDM0025E, and identifies the WIP record that is in error. The message contains the first 70 characters of the WIP record. The WIP prefix is located in the first eight characters of the record.
Action:
Correct the invalid WIP prefix. For a list of valid WIP prefixes and their meanings, see the Parallel Development Option Guide. After the WIP record has been corrected, resubmit the Merge request.
Reason:
An out-of-storage condition or an internal error has occurred.
Action:
If the reason code is NOSTG, increase the amount of storage available to the region. For other reason codes, contact CA Technical Support.
Reason:
Informational message.
Action:
Contact CA Technical Support if you cannot resolve the problem.
Reason:
All merging items must be CA Endevor SCM Elements, if the target of the merge is an CA Endevor SCM inventory location.
Action:
Merge to an output file, and then add the member into CA Endevor SCM.
Reason:
All merging items must be CA Endevor SCM Elements, if the target of the merge is an CA Endevor SCM Inventory location.
Action:
Merge to an output file then add the member into CA Endevor SCM.
Reason:
An incorrect type name was specified on the target CA Endevor SCM location.
Action:
Re-do the merge using the correct type name.
Reason:
The Build request specified a CA Endevor SCM location as the ROOT, DV1 or DV2 location. PDM was unable to locate the Environment, System, Subsystem, type, or Stage specified in the ROOT, DV1 or DV2 clause.
Action:
Correct the location field specified in the ROOT, DV1 or DV2 clause and identified by type. If the specified ROOT, DV1 or DV2 parameter was correct, verify that PDM is using the correct C1DEFLTS table.
Reason:
If PDM finds an explicit WIP member mask, it requires that the ROOT mask is also explicit. The Build request contained an explicit WIP member mask and a non-explicit (wildcarded) ROOT member mask. PDM will terminate the Build request.
Action:
Change the BUILD member mask to reflect the correct combination of WIP, ROOT, DV1 and DV2 member masks. If the WIP is explicit then the ROOT, DV1 and DV2 masks must also be explicit. If multiple Root members/Elements are to be processed, use a WIP member mask to generate the appropriate member name or explicitly list each of the Root files desired.
Reason:
PDM was unable to build a member or Element list for the file specified.
Action:
This message is usually generated because another error was detected. For any other error message, see the PDM Build WIP Detail Report. If another error message was generated then see the corrective action indicated for the message. If another error message was not found, verify that the location information was specified correctly in the Build request and that the member/Element mask statements are also valid.
Reason:
PDM was unable to locate the member or Element in the ROOT, DV1, DV2, or WIP file. PDM will terminate the current operation.
Action:
Verify that at least one member or Element matching the mask specified is found at the location specified and resubmit the Build or Merge request. If a matching member or Element is not found then specify another member/Element mask in the Build or Merge request.
Reason:
PDM was unable to locate the member or Element in the ROOT, DV1, DV2, or WIP file. PDM will terminate the current operation.
Action:
Verify that at least one member or Element matching the mask specified is found at the location specified and resubmit the Build or Merge request. If a matching member or Element is not found then specify another member/Element mask in the Build or Merge request.
Reason:
PDM was unable to locate the member or Element in the ROOT, DV1, DV2, or WIP file. PDM will terminate the current operation.
Action:
Verify that at least one member or Element matching the mask specified is found at the location specified and resubmit the Build or Merge request. If a matching member or Element is not found then specify another member/Element mask in the Build or Merge request.
Reason:
PDM was unable to locate the member or Element in the ROOT, DV1, DV2, or WIP file. PDM will terminate the current operation.
Action:
Verify that at least one member or Element matching the mask specified is found at the location specified and resubmit the Build or Merge request. If a matching member or Element is not found then specify another member/Element mask in the Build or Merge request.
Reason:
PDM was unable to locate the member or Element in the ROOT, DV1, DV2, or WIP file. PDM will terminate the current operation.
Action:
Verify that at least one member or Element matching the mask specified is found at the location specified and resubmit the Build or Merge request. If a matching member or Element is not found then specify another member/Element mask in the Build or Merge request.
Reason:
PDM determined that the logical record length (LRECL) of the WIP file is not large enough. The logical record length of the WIP file must be at least eight bytes larger then the largest record length of the Root, Derivation 1 or Derivation 2 files. If the WIP file contains variable length records then the WIP file must be at least 12 bytes larger. PDM will terminate the Build WIP processing.
Action:
Reallocate the WIP file with the correct record length and resubmit the Build WIP request.
Reason:
The BUILD WIP statement specified an invalid COMPARE from or COMPARE THRU value. The valid COMPARE column range is 1 through 256, inclusive. The COMPARE THRU value cannot be larger than the ROOT data set or Element record length. PDM will terminate the Build WIP processing.
Action:
Correct the COMPARE clause and resubmit the BUILD WIP request.
Reason:
The BUILD WIP statement specified a COMPARE from value that was larger than the COMPARE THRU value. The COMPARE THRU value must be greater than or equal to the COMPARE from value. PDM will terminate the Build WIP processing.
Action:
Correct the COMPARE clause and resubmit the Build WIP request.
Reason:
Build WIP processing determined that the identified data set was a CA Panvalet or CA Librarian data set and that CA Panvalet or CA Librarian data sets are not supported. PDM will terminate the Build WIP processing.
Action:
Specify a data set that is not a CA Panvalet or CA Librarian data set and resubmit the Build WIP request.
Reason:
The Element identified in the message is a sourceless Element and cannot be specified as a Root, DV1, or DV2 Element.
Action:
Use the actual Element associated to the sourceless Element.
Reason:
The PDM WIP specification for the Element identified on the PDM0049E message has a wrong version level. Log delta Elements are restricted to use the Element’s current version level since source is unavailable for prior levels.
Action:
Specify the current level.
Reason:
PDM has completed the Build WIP or Merge processing. The operation completed with the specified return code.
Action:
None. If the return code is non-zero, check the PDM Build WIP Detail Report for messages that may identify an error.
Reason:
The WRITE STATISTICS TO clause was specified in either a Build or Merge request. PDM has written the indicated number of statistics records to the specified data set.
Action:
None.
Reason:
An internal error occurred during PDM processing. PDM will terminate the current operation.
Action:
Resubmit the request. If the problem persists, contact your administrator.
Reason:
An internal error occurred during PDM statistics processing. PDM will terminate the current operation.
Action:
Resubmit the request. If the problem persists, contact your administrator.
Reason:
The Merge operation completed successfully and the specified WIP member was deleted. The Merge operation deletes the WIP member if OPTIONS DELETE WIP AFTER MERGE has been specified in the MERGE statement.
Action:
None.
Reason:
PDM could not locate the specified data set name in the System catalog. The identified action cannot continue processing.
Action:
Correct the data set name and resubmit the action that failed.
Reason:
The identified statistics data set had invalid attributes. The statistics data set must be sequential and must have variable length records or at least 533 bytes.
Action:
Reallocate the statistics data set with the correct attributes or specify a data set that has the correct attributes. Resubmit the request that failed.
Reason:
OPTIONS WRITE STATISTICS TO DDNAME was specified in the BUILD WIP or MERGE statement, but the DDname specified was not allocated to the PDM session. PDM will terminate the Build WIP or Merge processing.
Action:
If PDM is executing in batch mode, add the specified DDname to the PDM JCL. If PDM is executing in foreground, use the TSO ALLOCATE command to allocate the DDname to the TSO session.
Reason:
WRITE STATISTICS TO was specified in the BUILD WIP or MERGE statement. PDM also detected that the PDMSTATS DD statement was allocated. PDM will write the statistics to the data set identified in the WRITE STATISTICS TO clause. The PDMSTATS DD statement will be ignored.
Action:
None. To prevent the message from being issued, remove the PDMSTATS DD statement from the PDM execution JCL.
Reason:
Build WIP processing determined that the COMPARE THRU value specified is larger than the record length of the data set identified. PDM cannot compare data that is outside the bounds of a source record. PDM will terminate the Build WIP processing.
Action:
Correct the COMPARE THRU clause and resubmit the Build WIP request.
Reason:
The CA Panvalet or CA Librarian language specified in the OPTIONS LANGUAGE clause is not valid. PDM will terminate the Build WIP processing.
Action:
Correct the OPTIONS LANGUAGE clause and resubmit the Build WIP request.
Reason:
Build WIP processing detected an internal logic error in the routine identified. PDM will terminate the Build WIP processing.
Action:
Retry the Build WIP action. If the problem persists, contact your administrator.
Reason:
The CA Endevor SCM compare program, BC1PSCMP, returned a non-zero return code. PDM cannot continue with the Build WIP processing.
Action:
Check the PDM Build WIP Detail Report for additional error messages. Take any corrective action identified by those messages. If the error cannot be corrected, contact your administrator.
Reason:
PDM could not locate the statistics data set specified in the OPTIONS WRITE STATISTICS TO DSNAME in the System catalog. PDM will terminate the Build WIP or Merge processing.
Action:
Correct the WRITE STATISTICS TO DSNAME clause and resubmit the Build WIP or Merge request.
Reason:
PDM could not allocate the data set specified in the OPTIONS WRITE STATISTICS TO DSNAME clause. An error message identifying the Dynamic Allocation return code should precede this message. PDM will terminate the Build WIP or Merge processing.
Action:
See IBM publication GC28-1852 MVS/ESA System Programming Library: Application Development Guide or GC28-1303 OS/VS2 MVS Systems Programming Library: Job Management for a definition of the S99ERROR and S99INFO fields. Correct the error and resubmit the request.
Reason:
An unrecoverable I/O error occurred while PDM was accessing the identified data set. A specific I/O routine generated message should precede this message. PDM will terminate the Build WIP or Merge processing.
Action:
See the previous I/O routine error message and take any corrective action identified. Resubmit the Build WIP or Merge request.
Reason:
The CA Endevor SCM $IMR service returned an error condition when PDM accessed the Master Control File (MCF). The error message returned by the $IMR service will follow this message. PDM will terminate the Build
WIP processing.
Action:
See the $IMR message that follows this message, take any corrective action specified, and resubmit the Build WIP request.
Reason:
The CA Endevor SCM $SMR service returned an error condition when PDM attempted to retrieve the specified Element. The PDM Build WIP Detail report should contain an error message that identifies the $SMR error. PDM will terminate the Build WIP processing.
Action:
See the $SMR error message and take any corrective action specified. If the problem cannot be corrected, contact your administrator.
Reason:
An error occurred during PDM Build WIP or Merge initialization processing. A message that identifies the cause of the error should precede this message. PDM will terminate the Build WIP or Merge processing.
Action:
See any previous error message, take the corrective action identified, and resubmit the Build WIP or Merge request.
Action:
See any previous error message, take the corrective action identified, and resubmit the Build WIP request.
Reason:
The PDM Statistics routine passed a non-zero return code. PDM will terminate the Build WIP or Merge processing.
Action:
Retry the Build WIP or Merge request. If the problem persists, contact your administrator.
Reason:
PDM detected an unexpected end-of-file while reading the Root, Derivation 1 (DV1), or Derivation 2 (DV2) file during Build WIP processing. PDM will terminate the Build WIP processing.
Action:
Retry the Build WIP request. If the problem persists, contact your administrator.
Reason:
The internal structure returned by the CA Endevor SCM compare program is logically inconsistent. PDM will terminate the Build WIP processing.
Action:
Retry the Build WIP request. If the problem persists, contact your administrator.
Reason:
An error occurred during Build WIP processing. PDM was executing the Build WIP pass number identified. A previous message should identify the cause of the error. PDM will terminate the Build WIP processing.
Action:
See the previous error message, take any corrective action identified and resubmit the Build WIP request.
Reason:
PDM successfully completed the Build WIP processing. The Build WIP request specified the MERGE OUTPUT clause. PDM was unable to perform the Merge request because the MERGE OUTPUT member already exists and the REPLACE option was not specified. This is an informational message. PDM will continue with the Build WIP request.
Action:
If you want the WIP member to be merged, submit a separate request for the merge.
Reason:
The Build WIP request specified the MERGE OUTPUT clause. PDM has completed the Build WIP with no errors and is now beginning the Merge operation.
Action:
None.
Reason:
The PDM Build WIP action contained the MERGE OUTPUT clause. PDM will automatically merge the WIP file only if it finds no conflicts in the WIP file. The current WIP file had at least one conflict. PDM, therefore, will not perform the Merge operation as part of the Build WIP processing.
Action:
None. Resolve the conflicts with the Edit WIP function and use the Merge action to create the Merge file.
Reason:
A Build WIP member/Element was not specified with the BUILD WIP statement and the WIP, Root, Derivation 1 or Derivation 2 data set is not a sequential data set or the Root, Derivation 1 or Derivation 2 location is a Element. The Build WIP member/Element mask can be omitted only when the WIP, Root, Derivation 1 and Derivation 2 files are sequential data sets. In all other cases, PDM requires the Build WIP member/Element mask.
Action:
Add the appropriate Element/member mask statements to the BUILD WIP statement and resubmit the request.
Reason:
The WIP file specified in the MERGE statement is a non-sequential data set and an appropriate Merge member mask was not specified. PDM requires a Merge member mask if the WIP data set is non-sequential. PDM will terminate the Merge request.
Action:
Add the appropriate member mask statements to the MERGE statement and resubmit the request.
Reason:
The member mask specified for the identified file is incorrect for a sequential data set. If the file is sequential, the member mask specified must be '(N/A)'. PDM will terminate the Build WIP or Merge request.
Action:
Correct the member mask statement and resubmit the request.
Reason:
The BUILD WIP statement contained the MERGE OUTPUT clause. PDM successfully merged the WIP file into the identified data set after the Build WIP completed.
Action:
None.
Reason:
Informational message.
Action:
None.
Reason:
The BUILD WIP statement contained the OPTIONS DISABLE PERFORMANCE ENHANCEMENT clause. PDM will not use the performance enhancement for the identified file as part of the Build processing. By default, the performance enhancement is always enabled.
Action:
None.
Reason:
The logical record length (LRECL) of the Merge Output data set is not large enough to write the merged WIP records. The LRECL of the Merge data set must be greater than or equal to the LRECL of the WIP data set minus eight. For example, if the WIP data set LRECL is 88, the Merge data set LRECL must be at least 80. The four-byte RDW of variable length records is not included in the calculations. PDM will terminate the Merge processing.
Action:
Specify a Merge data set that has a sufficiently large LRECL or reallocate the Merge data set with an appropriate LRECL.
Reason:
PDM found an invalid internal control block structure. The message identifies the function code associated with the PDM Header Block structure. PDM will terminate any further processing.
Action:
Retry the operation. If the problem persists, contact your administrator.
Reason:
PDM was unable to dynamically allocate the data set specified. The dynamic allocation service returned the error code and information code identified. PDM will terminate the Build or Merge processing.
Action:
See IBM publication GC28-1852 MVS/ESA System Programming Library: Application Development Guide or GC28-1303 OS/VS2 MVS Systems Programming Library: Job Management for a definition of the S99ERROR and S99INFO fields. Correct the error and resubmit the request.
Reason:
PDM found that one of the data sets specified in the BUILD or MERGE statement was allocated to DD DUMMY or DD DSN=NULLFILE. PDM does not support DUMMY data sets for the BUILD ROOT, DV1 or DV2 files or the MERGE WIP file.
Action:
Specify a valid data set for the file that was in error and resubmit the request.
Reason:
PDM determined that the identified data set was a load module library, that is, the record format was Undefined (RECFM=U). PDM does not support load module libraries.
Action:
Replace the specified data set with a non-load module library and resubmit the request.
Reason:
The Merge operation uses a dynamically allocated, temporary data set during processing. PDM was unable to allocate the temporary data set. PDM will terminate the Merge operation.
Action:
See IBM publication GC28-1852 MVS/ESA System Programming Library: Application Development Guide or GC28-1303 OS/VS2 MVS Systems Programming Library: Job Management for a definition of the S99ERROR and S99INFO fields. Correct the error and resubmit the request. If the error persists, contact your Systems programming area.
Reason:
The Merge operation uses a dynamically allocated, temporary data set during processing. The temporary data set dynamically allocated by PDM did not meet the Merge operation validation requirements.
Action:
One or more error messages should have preceded message PDM0174E. Follow the corrective action indicated for the error messages and resubmit the request.
Reason:
PDM determined that the internal structure returned by the compare program, BC1PSCMP, is logically inconsistent with the return code received from BC1PSCMP. PDM is unable to complete the Build processing. This message may be issued if attempting to compare a ROOT, or DERIVATION entity that contains no source lines (an EMPTY member). An EMPTY member causes the line number table (LNT) to contain zero lines of source with which to compare. Because the count of the number of lines is zero, this message is issued.
Action:
If the source of the message is not due to the comparison of an EMPTY member, retry the Build request. If the problem persists, use the OPTIONS DISABLE PERFORMANCE ENHANCEMENT clause in the BUILD WIP statement to disable the Build WIP performance enhancement. If the problem still persists, contact your CA Endevor SCM Administrator.
Reason:
PDM determined that the internal structure returned by the compare program, BC1PSCMP, is logically inconsistent with the return code received from BC1PSCMP. PDM is unable to complete the Build processing.
Action:
Retry the Build request. If the problem persists, use the OPTIONS DISABLE PERFORMANCE ENHANCEMENT clause in the BUILD WIP statement to disable the Build WIP performance enhancement. If the problem still persists, contact your administrator.
Reason:
The MERGE statement contained the OPTIONS DISABLE PERFORMANCE ENHANCEMENT clause. PDM will not use the performance enhancement as part of the Merge processing. By default, the performance enhancement is always enabled.
Action:
None.
Reason:
An unrecoverable ABEND occurred during either BUILD or Merge processing. The abend code identifies the ABEND that occurred. PDM will immediately terminate processing.
Action:
If the abend code was an Sx37 ABEND, one of the PDM files ran out of space. See the System job log for the name of the data set that ran out of space. Increase the size of the data set and resubmit the request. If any other abend code occurred, retry the operation. If the problem persists, contact your administrator.
Reason:
One or more BUILD member/Element masks contained a ROOT or DV1 wildcard. While expanding the wildcarded member PDM was unable to match a Root member with a Derivation 1 member. The message identifies the names of the ROOT, DV1 and DV2 members that PDM could resolve. A member name containing 10 asterisks will identify the file for which PDM could not match a member. PDM processing will continue but the Build return code will be set to eight.
Action:
Specify one or more discrete member/Element masks in place of the wildcarded member/Element mask and resubmit the request.
Reason:
The Merge operation performed as part of Build processing completed with a non-zero return code. Build processing will continue, but the Build action return code will be set to eight. The WIP member will be valid. The Merge file will not be valid.
Action:
See the PDM Build WIP Detail Report for any other error message that would indicate the cause of the error. See the corrective action for the error message.
Reason:
Informational message.
Action:
None.
Reason:
An incompatible Root Element was used in the WIP process. The Root's last level source timestamp is not present in the derivation Element's change levels. Source statements may have been dropped.
Action:
Check results to make sure that the merge completed correctly, because PDM was not able to verify that the derivation was built from the Root.
Reason:
An incompatible Root Element was used in the WIP process. The Root's last level source timestamp is not present in the derivation Element's change levels. Source statements may have been dropped.
Action:
Check results to make sure that the merge completed correctly, because PDM was not able to verify that the derivation was built from the Root.
Reason:
PDM is beginning to parse the PDM control statements.
Action:
None.
Reason:
PDM has successfully completed parsing the control statements. No errors were detected by the parsing routine. PDM will begin processing the specified requests.
Action:
None.
Reason:
The PDM parsing routine detected one or more errors with the control statements specified. A message that identifies the error will be written to the PDM Syntax Request Report. PDM will terminate further processing.
Action:
See the error message issued, correct the control statements and resubmit the request.
Reason:
PDM was unable to open the Batch Request data set associated with the identified ddname. PDM will terminate further processing.
Action:
Verify that the Batch Request data set identified by the specified DDname has been allocated to the PDM session. Resubmit the request.
Reason:
The logical record length (LRECL) of the Batch Request data set is invalid. The LRECL must be 80 for fixed length records and 84 for variable length records. PDM will terminate further processing.
Action:
Reallocate the Batch Request data set with the appropriate logical record length and resubmit the request.
Reason:
The PDM Batch Request data set has an invalid record format. The data set must contain either fixed length or variable length records. PDM will terminate further processing.
Action:
Reallocate the Batch Request data set with the correct attributes and resubmit the request.
Reason:
The COMPARE THRU value is larger than the Element record length defined in the Element type record for the derivation identifier specified. PDM will terminate the BUILD action with a return code of 12.
Action:
The COMPARE THRU value must be no larger than the derivation file logical record length (LRECL). Respecify the COMPARE THRU value so that it is less than or equal to the data set LRECL identified. If the ROOT is an Element, the COMPARE column values are taken from the Element type record. In that case, either modify the ROOT Element type record or specify a different Element type.
Reason:
The COMPARE THRU value is larger than the logical length (LRECL) of the derivation file identified. PDM will terminate the BUILD action with a return code of 12.
Action:
The COMPARE THRU value must be no larger than the derivation file logical record length (LRECL). Respecify the COMPARE THRU value so that it is less than or equal to the data set LRECL identified. If the ROOT is an Element, the COMPARE column values are taken from the Element type record. In that case, either modify the ROOT Element type record or specify a different Element type.
Reason:
PDM did not create the WIP files as part of Build processing because the BUILD WIP statement specified the OPTIONS CREATE WIP NEVER clause.
Action:
None. If you want the WIP files to be created then remove the OPTIONS CREATE WIP NEVER clause and resubmit the Build WIP request.
Reason:
The WIP location parameter was not specified in the BUILD WIP statement. PDM requires a WIP DDNAME or a WIP DSNAME parameter.
Action:
Add the WIP DDNAME or WIP DSNAME clause to the BUILD WIP statement and resubmit the request.
Reason:
The required ROOT location information was not specified in the BUILD WIP statement.
Action:
Add the appropriate ROOT DDNAME, ROOT DSNAME or ROOT location information to the BUILD WIP statement and resubmit the request.
Reason:
The required Derivation 1 (DV1) location information was not specified in the BUILD WIP statement.
Action:
Add the appropriate DV1 DDNAME, DV1 DSNAME or DV1 location information to the BUILD WIP statement and resubmit the request.
Reason:
You must specify an output location on the PDM Merge statement.
Action:
Specify a Merge output location and resubmit the job.
Reason:
The required WIP location information was not specified in the MERGE statement.
Action:
Add the appropriate WIP DDNAME or WIP DSNAME to the MERGE statement and resubmit the request.
Reason:
A PDM member/Element mask statement was encountered but a valid BUILD WIP or MERGE statement was not found.
Action:
Verify that a valid BUILD WIP or MERGE statement was specified. Check the PDM Syntax Request Report for any previous error messages. Correct any previous errors or add a valid BUILD WIP or MERGE statement and resubmit the request.
Reason:
The OUTPUT member mask was found following a BUILD statement. The OUTPUT clause is valid only after a MERGE statement.
Action:
Remove the OUTPUT mask clause. The Build operation requires the ROOT, DV1, DV2, and WIP member mask clauses. The OUTPUT clause is used with the MERGE operation.
Reason:
The ROOT member mask was found following a MERGE statement. The ROOT clause is valid only after a BUILD statement.
Action:
Remove the Root mask clause. The MERGE operation requires the OUTPUT and WIP member mask clauses. The ROOT clause is used with the Build operation.
Reason:
The DV1 member mask was found following a MERGE statement. The DV1 clause is valid only after a BUILD statement.
Action:
Remove the DV1 mask clause. The Merge operation requires the OUTPUT and WIP member mask clauses. The DV1 clause is used with the Build operation.
Reason:
The DV2 member mask was found following a MERGE statement. The DV2 clause is valid only after a BUILD statement.
Action:
Remove the DV2 mask clause. The Merge operation requires the OUTPUT and WIP member mask clauses. The DV2 clause is used with the Build operation.
Reason:
A DV2 member/Element mask was specified but the BUILD statement did not contain a DV2 clause. The DV2 location must be defined if a DV2 mask is specified.
Action:
Either add a DV2 clause to the BUILD statement to define the DV2 location or remove the DV2 member/Element mask clause.
Reason:
Multiple locations were specified for a given file location in the BUILD or MERGE statement. For example, both WIP DSNAME and WIP DDNAME were specified. Only one definition for each location is allowed.
Action:
Remove the incorrect location specification from the BUILD or MERGE statement. Only one location definition can be specified.
Reason:
The CA Endevor SCM location for the ROOT, DV1 or DV2 clauses were either missing keywords, or contained incorrect values.
Action:
Correct the CA Endevor SCM location specification of the ROOT, DV1, and DV2 clauses. Make sure the ENVIRONMENT, SYSTEM, SUBSYSTEM, TYPE and STAGE keywords are all specified and that they contain correct values.
Reason:
A location was specified for the ROOT, DV1 or DV2 location and the LEVEL option was also specified but the level specified was not in the range 00 through 99, inclusive.
Action:
Specify a level number that is in the range 00 through 99, or remove the LEVEL keyword to use the current level of the Element.
Reason:
The ROOT member/Element mask specified is blank. A non-blank member/Element mask is required.
Action:
Specify the appropriate, non-blank member mask in the ROOT clause.
Reason:
The OUTPUT member mask specified is blank. A non-blank member mask is required.
Action:
Specify the appropriate, non-blank member mask in the OUTPUT clause.
Reason:
The required Derivation 2 (DV2) location information was not specified in the PDM BUILD statement.
Action:
Add the appropriate DV2 DDNAME, DV2 DSNAME or DV2 location information to the BUILD statement and resubmit the request.
Reason:
An location was specified for the ROOT, DV1 or DV2 location and the VERSION option was also specified but the version specified was not in the range 00 through 99, inclusive.
Action:
Specify a version number that is in the range 00 through 99, or remove the VERSION keyword to use the current level of the Element.
Reason:
The STATS statement was found but the statement parameters were coded incorrectly. The format of the STATS statement is STATS OFF DETAIL or STATS OFF ALL.
Action:
Correct the STATS statement syntax. Specify STATS OFF ALL to suppress all PDM reports or STATS OFF DETAIL to suppress the PDM Detail Report.
Reason:
The ROOT member/Element mask specified contains one or more invalid characters.
Action:
Correct the member/Element mask value. For the member/Element naming convention, see the Parallel Development Option Guide.
Reason:
The DV1 member/Element mask specified contains one or more invalid characters.
Action:
Correct the member/Element mask value. For the member/Element naming convention, see the Parallel Development Option Guide.
Reason:
The DV2 member/Element mask specified contains one or more invalid characters.
Action:
Correct the member/Element mask value. For the member/Element naming convention, see the Parallel Development Option Guide.
Reason:
The WIP member mask specified contains one or more invalid characters.
Action:
Correct the member mask value. For the member naming convention, see the Parallel Development Option Guide.
Reason:
The OUTPUT member/Element mask specified contains one or more invalid characters.
Action:
Correct the member mask value. For the member naming convention, see the Parallel Development Option Guide.
Reason:
A PDM BUILD, MERGE, STATS or mask statement was not terminated with a period. PDM syntax rules require that all statements end with a period.
Action:
Add the missing period to the PDM statement. Also verify that no other errors were detected with the PDM control statements. If any other errors were detected, correct those errors and resubmit the request.
Reason:
The PDM batch interface was executed but the Batch Request data set did not contain any valid PDM control statements.
Action:
Verify that the correct Batch Request data set was specified. Also, verify that the PDM control statements specified are syntactically correct. For any errors with the PDM control statements, see the PDM Syntax Request Report.
Reason:
The DV1 member/Element specified is blank. A non-blank member/Element mask is required.
Action:
Specify the appropriate, non-blank member mask in the Derivation 1 clause.
Reason:
The DV2 member/Element specified is blank. A non-blank member/Element mask is required.
Action:
Specify the appropriate, non-blank member mask in the DV2 clause.
Reason:
The BUILD WIP COMPARE from column value specified is non-numeric. The clause can contain only numeric characters in the range 1 to 256, inclusive.
Action:
Correct the COMPARE from value specified in the BUILD WIP statement.
Reason:
The Build WIP COMPARE THRU column value specified is non-numeric. The clause can contain only numeric characters in the range 1 to 256, inclusive.
Action:
Correct the COMPARE THRU value specified in the BUILD WIP statement.
Reason:
The DDNAME or DSNAME specified in the WRITE STATISTICS TO clause contained a blank value. The DDNAME or DSNAME must specify a valid, non-blank identifier.
Action:
Correct the WRITE STATISTICS TO clause so that a valid identifier is specified with the DDNAME or DSNAME keyword.
Reason:
The WRITE STATISTICS TO clause must contain a DDNAME or a DSNAME but it cannot contain both keywords.
Action:
Correct the WRITE STATISTICS TO clause so that only the DDNAME or the DSNAME keyword is specified.
Reason:
The Build WIP request cannot contain a MERGE OUTPUT clause if the OPTIONS CREATE WIP NEVER clause is also specified.
Action:
Remove either the MERGE OUTPUT clause or the OPTIONS CREATE WIP NEVER clause from the Build request.
Reason:
You must specify an output location on the BUILD WIP MERGE OUTPUT statement.
Action:
Specify a Merge output location and resubmit the job.
Reason:
The OPTIONS DELETE WIP AFTER MERGE clause was specified in the Build request but the MERGE OUTPUT clause was not also specified. PDM will ignore the OPTIONS DELETE WIP AFTER MERGE clause.
Action:
None. To eliminate the message, remove the OPTIONS DELETE WIP AFTER MERGE clause from the Build request.
Reason:
The OPTIONS LANGUAGE clause was specified in the Build request but the MERGE OUTPUT clause was not also specified. PDM will ignore the OPTIONS LANGUAGE clause.
Action:
None. To eliminate the message, remove the OPTIONS LANGUAGE clause from the Build request.
Reason:
An output CA Endevor SCM location was specified for the merge. The Environment name used is invalid.
Action:
Specify a correct Environment name and resubmit the job.
Reason:
An output CA Endevor SCM location was specified for the merge. The System name used is invalid.
Action:
Specify a correct System name and resubmit the job.
Reason:
An output CA Endevor SCM location was specified for the merge. The Subsystem name is invalid.
Action:
Specify a correct Subsystem name and resubmit the job.
Reason:
An output CA Endevor SCM location was specified for the merge. The type name is invalid.
Action:
Specify a correct type name and resubmit the job.
Reason:
An output CA Endevor SCM location was specified for the merge. The Stage is invalid.
Action:
Specify a correct Stage name and resubmit the job.
Reason:
The processor group name is not defined for the type specified on the merge output CA Endevor SCM location.
Action:
Specify a correct processor group name and resubmit the job.
Reason:
The DELETE NDVR DV1 DV2 clause is only applicable when the merge is to an CA Endevor SCM location.
Action:
Nothing.
Reason:
The SYNC NDVR OUTPUT clause is only applicable when the merge is to an CA Endevor SCM location.
Action:
Nothing.
Reason:
The BYPASS GENERATE PROCESSOR clause is only applicable when the merge is to an CA Endevor SCM location.
Action:
Nothing.
Reason:
The PROCESSOR GROUP NAME clause is only applicable when the merge is to an CA Endevor SCM location.
Action:
Nothing.
Reason:
The PDM Build WIP I/O routine received an error from the $BSTGLST service. The $BSTGLST service that was invoked is identified by function. The $BSTGLST service returned the error code identified by result code
Action:
If the named function is ACQUIRE or INIT and the named result code is $BGETSTG, it implied that PDM was unable to obtain virtual storage for the request.
If PDM is executing in batch mode, increase the REGION parameter specified in the PDM batch EXEC or JOB JCL statement. If PDM is executing in foreground mode, signon to TSO with a larger region size.
For any other result code, retry the operation. If the problem persists use the OPTIONS DISABLE PERFORMANCE ENHANCEMENT clause in the BUILD or MERGE statement or set the disable the build wip and merge performance enhancement on the PDM User Defaults screen to Y. For more information on these actions, see the Parallel Development Option Guide.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|