Merge and Reconcile (M&R) Messages and Codes

M+R is an application under TSO/ISPF. As such, messages typically appear in short form in the upper right corner of the screen and in long form only if Help [PF1] is entered.

This appendix lists messages from M+R. The messages in series SERnnnA may require an action to rectify the situation evoking the message. Other messages, in series SERnnnI, are informational and require no action.

Messages are listed numerically by short message, followed by the long message, then an explanation, and finally, the required action (where needed).

Important

Please note; SERnnnn messages in Chapter 2 of this manual are for SerNet messages. SerNet messages begin with SER followed by 4 digits. M&R messages begin with SER followed by 3 digits SERnnn.

`SER001A` `M+R not licensed! | M+R not licensed for your use; Contact local help desk.`

Explanation: M+R is a separately licensed product. The software, as installed, has detected that M+R has not been licensed and refuses to continue.

Solution: If you get the message above and wish to investigate M+R further, contact your marketing representative.

`SER002A` `M+R license has expired! | M+R license has expired; Contact local help desk.`

Explanation: M+R is a separately licensed product. The software, as installed, has detected that M+R license has expired.

Solution: If you get the message above and wish to continue to use M+R, contact your marketing representative.

`SER003A` `SER003A Invalid option | Enter one of the listed options.`

Explanation: A menu has been presented and the only acceptable response is one of the listed options.

Solution: Action; Enter one of the listed options or exit.

`SER004A` `Invalid TEXT Type | Valid TEXT: BAL, C, COBOL, FORTRAN, JCL, NATURAL, PANEL, PLI, REXX, and RPG.`

Explanation: You have attempted to update your personal profile with a TEXT Type that has been misspelled. The long message above is a common subject of the entire list.

Solution: Action; Spell the TEXT Type correctly or enter a period (.) as a wildcard so that M+R can dynamically determine the columns to compare. Whatever is chosen can also be prefixed with a dollar ($) sign to suppress ignoring of spaces in the comparison.

`SER005A` `Must be SEQ | Print File must be SEQuentially organized.`

Explanation: You have attempted to update your personal profile for Print with a Data Set Name for Print that is not SEQuential (DSORG=PS).

Solution: Action; Change the data set name and M+R will automatically allocate it with proper attributes.

`SER006A` `Modules(s) not Loaded! | At least one module not loaded; Unable to proceed.`

Explanation: At initialization, M+R attempts to load modules required for its work. If it is unsuccessful, M+R terminates.

Solution: Action; Verify that your TSO logon procedure points to the M+R load library.

`SER007A` `Must be PDS or SEQ | "Work In Suspense" File must be Partitioned or SEQ Data Set.`

Explanation: You have attempted to update your personal profile with a Data Set Name for your WIS file that is neither PDS nor SEQuential.

Solution: Action; Change the data set name and M+R will automatically allocate it with proper attributes.

`SER008I` `Changed Versions | At least one version:{``change``}; Number of same versions: {``number``}.`

Explanation: At least one version: {change}; number of same versions: {number}.

Solution: Information; You have changed the base or derivative data sets or both. {change} can be any combination of the words “added," “moved," and “dropped" which describe your changes. {number} is the number of same versions, although not necessarily in the previous order.

`SER009I` `Profile updated. | Profile updated as entered for this and future sessions.`

Explanation: Information, the personal profile has been updated permanently. It applies for the rest of this session and future sessions until updated (in place) again. No action is required.

`SER010A` `I/O error | Input/Output error detected; Unable to proceed.`

Explanation: A file Input or Output error has been detected. The more common symptom is specifically described under message SER037A below. This is the catch-all message for other errors. One of the files specified under Profile Data Sets or VERSIONS has experienced an input error of undetermined origin. One of the possible reasons is the specification of PAN or LIB for a file that indeed is neither CA Panvalet nor CA Librarian, but that generally precipitates SER019A OPEN failure.

Solution: Split the screen and inspect the file with option 3.2 of ISPF. If it appears normal, attempt to browse (ISPF Option 1) the file.

`SER011A` `DSNAME missing | Base DSNAME missing or derivative DSNs not continuous, please enter.`

Explanation: An attempt has been made to specify data set names with an empty slot or these are not data sets. The minimum specification is a base. Derivatives 1 - 7 (Drv1 to Drv7) must be contiguous, i.e., no gaps. The cursor is placed at the perceived gap data set name.

Solution: Respecify the versions such that there are no gaps or supply at least a base data set.

`SER012A` `Allocation Failure | Data set not cataloged or under exclusive control; CANcel or change.`

Explanation: An attempt has been made to specify data set name that could not be allocated to the session. The cursor is placed at the offending data set name.

Solution: Probable user error in spelling the data set name or the data set is being exclusively allocated to another task. For example, an M+R batch job may be running that writes to the Print and/or WIS data set. NOTE Also remember that TSO ID and/or user prefix are not assumed. Full specification is always required in M+R.

`SER013A` `TYPE invalid | TYPE must be PDS, SEQ, PAN, LIB, or blank.`

Explanation: An attempt has been made to specify a TYPE and was misspelled. The cursor is placed at the offending TYPE. Valid literals and their meanings are:

PDS - Partitioned Data Set, (DSORG=PO) includes PDSE
SEQ - Sequential, DSORG=PS
PAN - CA Panvalet
LIB - CA Librarian

Solution: If PAN or LIB, specify accordingly. Otherwise, we recommend leave it blank for M+R to determine.

`SER014A` `MEMBER invalid | MEMBER must be alphanumeric starting with alpha, @, #, or $.`

Explanation: An attempt has been made to specify a MEMBER that is considered invalid. It must follow the rules for a PDS member name with the exception that it can be nine or ten characters long only if the version data set is PAN. The cursor is placed at the offending MEMBER.

Solution: Specify correctly. Specify a pattern (ABC*) or leave it blank to get a member list.

`SER015A` `MEMBER invalid | MEMBER name can be longer than 8 chars only if PANvalet.`

Explanation: An attempt has been made to specify a MEMBER that is longer than eight characters and TYPE was not specified as PAN. The cursor is placed at the offending MEMBER.

Solution: Respecify MEMBER name with a maximum of eight alphanumeric characters.

`SESR016A` `Pattern, Base only | A member pattern is applicable only to the Base data set.`

Explanation: An attempt has been made to specify a pattern for MEMBER of a derivative. This facility is only applicable to the base. The cursor is placed at the offending MEMBER.

Solution: Blank out the offending MEMBER name.

`SER017A` `MEMBER Must Be blank | MEMBER name must be blank for SEQuential data sets.`

Explanation: An attempt has been made to specify a MEMBER and the data set was specified as SEQ or dynamically discovered to be DSORG=PS. The cursor is placed at the offending MEMBER.

Solution: Blank out the offending MEMBER name.

`SER018A` `TYPE inconsistent | TYPE inconsistent with data set organization.`

Explanation: An attempt has been made to specify a TYPE that is inconsistent with what was dynamically discovered; for example, TYPE=PDS was specified and the data set is not a PDS; TYPE was specified as SEQ, PAN, or LIB, and the data set is really a PDS. The cursor is placed at the offending TYPE.

Solution: Correct the offending TYPE.

`SER019A` `OPEN failure | Unable to OPEN the specified data set.`

Explanation: An attempt has been made to OPEN a data set and it failed. Probable cause is an error in the specification for PAN or LIB. The cursor is placed at the offending DSNAME.

Solution: Split the screen and inspect the file with option 3.2 of ISPF.

`SER020A` `Invalid DSORG | Data set organization (DSORG) unacceptable, e.g. VSAM.`

Explanation: A data set was allocated as specified but was discovered to have an organization (DSORG) that cannot be handled, such as VSAM. The cursor is placed at the offending DSNAME.

Solution: Respecify the offending DSNAME.

`SER021A` `Invalid RECFM | Record Format (RECFM) unacceptable, e.g. Undefined.`

Explanation: A data set was allocated as specified but was discovered to have a record format (RECFM) that cannot be handled, such as Undefined, which implies a load library. The cursor is placed at the offending DSNAME.

Solution: Respecify the offending DSNAME.

`SER022A` `Member not found | &XXX member not found in {``name/ownerid``}.`

Explanation: An attempt has been made to specify a MEMBER name that could not be found. The cursor is placed at the offending MEMBER. XXXX is the member name; {name/ownerid} is either “base" or “derivative."

Solution: Specify correctly. Specify a pattern (ABC*) for base MEMBER or leave it blank to get a member list.

`SER023A` `Nothing to Execute | Versions not set; No work in suspense; Nothing to edit.`

Explanation: An attempt has been made to EXECUTE (option 2), EDIT (option 5), EXPORT (option 6), or for an ANALYSIS (option 7) on the Member Reconciliation menu and there was nothing in place yet to process in this session.

Solution: Set the VERSIONS (option 1), or LOAD a prior WIS.

`SER024A` `No members | No members match the specified criteria (pattern, range or mask).`

Explanation: An attempt has been made to EXECUTE (option 2) on the Member Reconciliation menu or to invoke the Consolidation Workplace panel (option 3) on the other tool menus, and it was determined that the specified base library had no members that matched the MEMBER pattern, range, or mask. Also, the library may be empty.

Solution: If the library is empty, pick another library or determine the reason for it being empty. If a pattern was used, make it less restrictive—instead of ABC*, use A*. If a range (first/last member name or pattern) was used, check the directory and make it more inclusive.

`SER025A` `Bad pattern | Member pattern ("*") must fit within first 8 characters.`

Explanation: An attempt has been made to specify a pattern for MEMBER that is considered invalid. The cursor is placed at the offending MEMBER.

Solution: The pattern delimiter (*) must exist within the first eight characters and be followed by all blanks. This is true even if the library is PANvalet.

`SER026A` `Invalid ID | ID field must be an alphabetic character “A" to “Z".`

Explanation: An attempt has been made to specify an ID that is considered invalid. Only alphabetic characters in the range “A" to “Z" are allowed. The cursor is placed at the offending ID.

Solution: Specify a unique character for ID of this derivative, thus avoiding any confusion when the Reconcile panel is presented.

`SER027A` `Duplicate ID | ID field must be unique — reenter ID.`

Explanation: An attempt has been made to specify an ID that is not unique, i.e., the same character already has been used as an ID for another derivative. The cursor is placed at the offending ID.

Solution: Specify a unique character for ID of this derivative, thus avoiding any confusion when the Reconcile panel is presented.

`SER028A` `Inconsistent DSORG | Data set organization (DSORG) inconsistent with findings.`

Explanation: A data set for export was allocated as specified but was discovered to have an organization (DSORG) inconsistent with what was specified: PDS for SEQ, PAN for PDS. The cursor is placed at the Export DSORG.

Solution: Respecify the offending DSORG or Export DSNAME.

`SER029I` `Versions accepted | Data set names specified as versions have been accepted.`

Solution: Information, this message acknowledges that you have passed all validations and allocations for the specifications. No action is required.

`SER030I` `Print complete | Printed report formatted in file “Print DSNAME".`

Explanation: This message acknowledges that you made an attempt to PRINT (option 5P), EXP PRINT (option 6P), or ANL PRINT (option 7P), on the Member Reconciliation menu, or to Print on the Consolidation Workplace panel, and it was successful. No action is required.

Solution: Information; Optionally, you can browse (ISPF option 1) the Print DSNAME as specified on Profile Data Sets panel. You may also route the file to a local printer outside of M+R.

`SER031A` `Execution required | Consolidation (Option 2, EXECUTE) required first.`

Explanation: An attempt has been made to SAVE a WIS (option 3) on the Member Reconciliation menu but there was nothing in place yet to save in this session.

Solution: Either set the VERSIONS and EXECUTE, or LOAD a prior WIS.

`SER032A` `"WIS" Loaded | "Work In Suspense" from prior session loaded; Ready to edit.`

Explanation: An attempt has been made to LOAD a prior WIS (option 4) on Member Reconciliation menu but the file was found to be empty or the selected member was not found in the WIS library.

Solution: Set the VERSIONS (option 1) and EXECUTE (option 2) in order to populate the WIS file before attempting to LOAD again.

`SER033I` `“WIS" Loaded | “Work In Suspense" from prior session loaded; ready to edit.`

Explanation: This message acknowledges that you have attempted, on the Member Reconciliation menu, to LOAD (option 3) a WIS from a prior session and were successful. No action is required.

`SER034I` `Must be SEQ | “Work In Suspense" must be SEQuential file for Member Reconciliation.`

Explanation: An attempt has been made to validate the profile settings (option 0) on the Member Reconciliation menu, but the specified WIS data set is not a sequential file. If you enter a new DSNAME, M+R will allocate it for you.

`SER035I` `Export complete | Consolidation effort successfully exported to external file.`

Explanation: This message acknowledges that you have attempted to EXPORT (option 6) on the Member Reconciliation menu or, on the Consolidation Workplace panel, to issue an Export line command and were successful. No action is required.

`SER036I` `“WIS" Saved | “Work In Suspense" saved for future session.`

Explanation: This message acknowledges that you have ENDed the reconciliation on the Reconcile panel or attempted to SAVE (option 3) a consolidation effort on the Member Reconciliation menu, and were successful. No action is required.

`SER037A` `Abend Sx37 | Target file full; Compress/reallocate before proceeding.`

Explanation: An attempt to write to an output file failed because of an x37 abend: B37, D37, E37. The cursor is positioned to the file involved.

Solution: Split the screen and inspect the file with option 3.2 of ISPF. If the file is a PDS, a library compress will probably be sufficient unless all directory blocks are consumed. NOTE If the file is SEQuential, you have to reallocate it with larger dimensions and try again.

`SER038A` `“WIS" data invalid | “Work In Suspense" has invalid data; Considered unusable due to {``reason``}.`

Explanation: An attempt has been made to LOAD a prior WIS (option 4) on the Member Reconciliation menu, but the data was found to be invalid and LOAD failed with a reason code ZZ, as follows:

40 - WIS perceived as empty

41 - Lengths of the statistics record out-of-sync

42 - No Base/Delta record found

43 - Lengths of a Base record out-of-sync

44 - No Delta record found

45 - Lengths of an Analysis record out-of-sync

46 - Delta Table missing

47 - Lengths of a Delta record out-of-sync

48 - No Delta Table entry found

49 - No End-of-Delta-Table found

4A - More than 8 Delta Table entries found

4B - WIS file continues after End-of-Delta-Table

4C - Previous Delta Deck 1st record lost

4D - Base record search out-of-sync

4E - Base record search abruptly ended

4F - Base record search unsuccessfully ended

F0 - Delta Deck last record lost while switch to a new set of decks

F1 - Delta Deck last record lost while switch to a new deck

Solution: Set the VERSIONS (option 1) and EXECUTE (option 2) in order to populate the WIS file before attempting to LOAD again. If this message persists, write down the reason code and contact your local help desk.

`SER039I` `Analysis complete | Analysis of consolidation effort completed.`

Explanation: This message acknowledges that you have attempted to perform ANALYSIS (option 7) on the Member Reconciliation menu, or to issue Analysis line command on the Consolidation Workplace panel and were successful. No action is required.

`SER040I` `Request Cancel''d | Your request has been CANCEL''d as directed.`

Explanation: This message acknowledges that you have entered CANcel (or abbreviated CAN) on the command line to exit immediately. No action is required.

`SER041A` `Export error | Output error of undetermined origin at export time.`

Explanation: An attempt has been made to export a consolidation effort and an output error has been uncovered. Action: Most likely PAN (CA Panvalet) or LIB (CA Librarian) has been selected as the data set organization for the export file. Try to access the file outside M+R and rectify any adverse conditions.

`SER042A` `Invalid command | Use “S" Select, “F" Force, “P" Print, “E" Export, or “A" Analysis.`

Explanation: An attempt has been made to issue a line command from the Consolidation Workplace panel which is illegal. Action: Enter “S" to execute or load a member from WIS, or “F" to force the execution of a member, or “P" to print the last view of a just-edited member, or “E" to export a justreconciled member, or “A" to analyze an executed or exported member.

`SER043A` `Unresolved Conflicts | Export with Unresolved Conflicts NOT allowed - Profile Setting.`

Explanation: An attempt has been made to export a consolidation effort with unresolved conflicts while the profile setting “Export Conflicts" is NO.

Solution: Either resolved the conflicts and try to export or change the profile setting of “Export Conflicts" to YES.

`SER044A` `MEMBER Range Invalid | Last Member name in range NOT greater than Starting Base MEMBER.`

Explanation: An attempt has been made to validate the input on Versions panel (option 1). The required range of member names is invalid due to last member name being greater than the first member name.

Solution: Either swap the first/last member names or enter a valid range.

`SER045I` `Must be PDS RECFM = VB | "Work In Suspense" WIS must be PDS, RECFM = VB, LRECL > 273.`

Explanation: This message warns you that the WIS data set specified on the Profile Data Sets panel must be PDS with proper DCB parameters. If you enter a new DSNAME, M+R will allocate it for you.

`SER046A` `Empty file | Member or sequential file does not contain any records.`

Explanation: The base file is considered empty. The cursor is positioned to the base DSNAME or member.

Solution: Respecify the base DSNAME if SEQuential or select a different member if PDS, PAN, or LIB type.

`SER047A` `SERBUILD return code 08 | SERBUILD processing failed with reason code (return code).`

The SERBUILD program has encountered a non-recoverable condition and cannot complete the processing due to a hexadecimal reason ZZ as follows:

06 - Data record length error

07 - Bottom-Of-Data missing

08 - Conflict Setting - lower limit greater than upper limit

09 - End-Of-DB missing while retrieving base records

0F - Unknown Function

10 - End-Of-DB missing while freeing trapped base records

20 - Merge out-of-sync

21 - Base record not found while processing CPX directive

22 - Delta Hex ID not found in NUMTABLE

23 - User Delta Hex ID not found in DELTABLE

24 - No address of base file in storage

25 - No Entry Point Address of ISPLINK

26 - No Entry Point Address of SERBSAM

27 - No Entry Point Address of Comparex

28 - No Entry Point Address of M+RPANEL

29 - Not EXECUTE/LOAD on First Call

2A - PCA address/indicator conflict on Next Call

2B - DB address invalid on Next Call

2C - DB address/indicator conflict on Next Call

2D - Delta Table address/indicator conflict on Next Call

2E - DYNPANEL Area address/indicator conflict on Next Call

2F - Response Area address/indicator conflict on Next Call

30 - DB missing on SAVE Call

31 - WIS file in storage address NOT cleared

39 - End-Of-DB missing while saving Base records

3A - End-Of-DB missing while saving Delta records

50 - DB missing on EDIT Call

5D - ISPF variables definition failure

60 - DB missing on EXPORT Call

69 - End-Of-DB missing

70 - DB missing on ANALYSIS Call

71 - Banner desk restructuring miss

74 - Invalid request to M+RPANEL

77 - Delta Hex ID invalid

78 - No Delta record found for stats record

79 - User Delta ID not found

7A - Zero divider

7B - First User Delta record not blank

7C - First User Delta record not found

7D - No Delta record found for appending

7E - Unknown Analysis Request

7F - Analysis deck missing

96 - JCL scan End-Of-DB missing

97 - JCL substitution End-Of-DB missing

98 - JCL substitution PROC statement out-of-cinch

99 - JCL scan/substitute/CPY scan redundant deck

9A - JCL scan out-of-sync

9B - JCL expand out-of-sync

9D - CPY scan End-of-DB missing

A0 - DB missing on PRINTRCN Call

B0 - DB missing on PRINT Call

C0 - DB missing on PRINTANL Call

F2 - No address of “WIS" file in storage

Solution: Write down the SERBUILD hexadecimal reason code ZZ and contact your local help desk.

`SER048A` `SERBSAM Return Non-Zero | File in Storage Handling failed with return code ZZ.`

Explanation: The SERBSAM program which handles Files in Storage has completed with a non- zero return code ZZ.

Solution: Write down the SERBSAM return code ZZ and contact your local help desk.

`SER049A` `COMPARE Return > 4 | Comparison of base to derivative failed with return code ZZ.`

Explanation: The text comparison of the base to one of the derivatives has failed with a return code ZZ greater than 4.

Solution: Write down the return code ZZ and contact your local help desk.

`SER050A` `Appl/Package invalid | ChangeMan ZMF application or change package invalid; Format xxxx999999.`

Explanation: The ChangeMan ZMF application or change package specified is invalid. Format is as follows: xxxx999999, where xxxx is the four character application mnemonic and 999999 is the package number.

Solution: Verify that the ChangeMan ZMF application mnemonic and the package number are in the correct format, and respecify.

`SER051A` `Appl/Package not found | ChangeMan ZMF application or change package not found.`

Explanation: The application or change package specified does not exist for this ChangeMan ZMF instance.

Solution: Verify the existence of the application or change package under this ChangeMan ZMF instance.

`SER052A` `Export CMN package | ChangeMan ZMF package required for export; Application insufficient.`

Explanation: The M+R/ChangeMan ZMF interface requires a change package number to export the consolidation effort to a ChangeMan ZMF Staging library.

Solution: Specify the ChangeMan ZMF package number and corresponding library type to be used as the target of the export of the consolidation effort.

`SER053A` `Export CMN status | ChangeMan ZMF change package for export must be in "DEV" status.`

Explanation: The M+R/ChangeMan ZMF interface requires a change package in “development" status to export the consolidation file to the staging library.

Solution: Specify a change package which is in development status or revert the package to development status.

`SER054I` `Export CMN pkg complete | Consolidation effort successfully exported to ChangeMan package.`

Explanation: This message acknowledges that you have attempted to EXPORT (option 6) on the Member Reconciliation menu, or to issue an Export line command on the Consolidation Workplace panel, for a consolidation effort to a ChangeMan ZMF change package and were successful. No action is required.

`SER055A` `LibType not found | ChangeMan ZMF library type not found in specified application.`

Explanation: The specified library type is not valid under this ChangeMan ZMF application.

Solution: Verify that this library type is valid for this application using the ChangeMan ZMF Local Administration function.

`SER056A` `LibType required | ChangeMan ZMF library type is required.`

Explanation: The library type is required if a ChangeMan ZMF application/package has been specified.

Solution: Enter the appropriate ChangeMan ZMF library type to be processed.

`SER057A` `Cannot export to package | Profile Export data set is not PDS or SEQ; update your profile.`

Explanation: The DSORG of the Export DSNAME data set is not PDS or SEQ. As M+R first exports to that data set and then from it to a ChangeMan ZMF package, it needs to be either PDS or SEQ.

Solution: If you want to export to a ChangeMan ZMF package, change the Export DSNAME to a data set with DSORG either PDS or SEQ on the Profile Data Sets panel.

`SER058I` `Unresolved Conflicts | Either Edit to solve or try again to export with records in conflict.`

Explanation: The user has attempted to export a reconciliation when unresolved conflicts exist.

Solution: You may ignore this warning by repeating the export request, or return to the Reconcile panel to resolve the conflicts and then try to export.

`SER059I` `"WIS" Will be overlaid | Current work not Saved or Exported; it will be lost on Execute/Load.`

Explanation: The user has attempted to execute a new reconciliation or load a previously saved WIS file when the current reconciliation is neither Saved nor Exported; this way, it will be lost. Information: You may ignore this warning by repeating the eXecute/Load request, or you may first Save/Export your current work.

`SER060A` `Invalid command | Follow Primary Command with space and an argument up to 8 char long.`

Explanation: You have entered what appears to be a “Locate" (abbreviated L) or “Create" (C) command without an argument.

Solution: Reenter the command with a legal argument, such as a name.

`SER061A` `MOVE/COPY is Pending | Enter “M", “C", “MM", or “CC" line command, or PASte, or RESet.`

Explanation: You have entered a destination command (“A" or “B") and the source move/copy or PASte command is pending.

Solution: Enter “M", “C", “MM", or “CC" line commands, or PASte command, or the RESet primary command without any argument.

`SER062A` `Command conflict | Enter “M", “C", “MM", or “CC" line command, or PASte, or RESet.`

Explanation: You have entered a destination move/copy command (“A" or “B") and then something other than source move/copy command(s) or PASte.

Solution: Blank out and enter, or override with, “M", “C", “MM", or “CC" source command(s), or enter PASte command, or the RESet primary command without any argument.

`SER063A` `Command RESet | This syntax was invalid; Please reenter the command.`

Explanation: You have entered an invalid combination of commands which causes the system to internally reset itself.

Solution: Reenter a valid combination of commands.

`SER064A` `Invalid argument | Enter numeric or space for a line command argument or RESet.`

Explanation: You have entered a line command argument which is neither a numeric nor a space.

Solution: Set the line command argument to either numeric or space (the default argument of “1" will be supplied).

`SER065A` `MOVE/COPY is Pending | Enter “A" or “B" line command, or CUT, or EXPort, or RESet.`

Explanation: You have entered a move/copy source command(s) (“M", “C", “MM", or “CC") and the destination command is pending.

Solution: Enter an “A" or “B" destination command, or CUT, or the RESet primary command without any argument.

`SER066A` `Command conflict | Enter “A" or “B" line command, or CUT, or RESet.`

Explanation: You have entered move/copy source command(s) (“M", “C", “MM", or “CC") followed by input other than a move/copy destination command.

Solution: Blank out and enter, or override with, an “A" or “B" line command, or enter CUT or the RESet primary command without any argument.

`SER067A` `&BLKPEND Pending | Enter &BLKPEND and “A" or “B" line commands, or CUT, or RESet.`

Explanation: You have entered one block move/copy command (“MM" or “CC"); the corresponding block command and the destination command are pending.

Solution: Complete the initiated block move/copy command and enter a destination command or CUT command. Otherwise, enter the RESet primary command without any argument.

`SER068A` `Command conflict | Enter “MM" or “CC" and “A" or “B" line commands, or CUT, or RESet.`

Explanation: You have entered a block move/copy command (“MM" or “CC"), then something other than the corresponding block command or a destination command.

Solution: Blank out or override, then complete the initiated block move/copy command, or enter a destination command or CUT command. Otherwise, enter the RESet primary command without any argument.

`SER069A` `RESet - Cmd Conflict | Command processing interrupted; enter RESet to continue.`

Explanation: You have entered an invalid combination of commands which causes the system to request a user-initiated reset.

Solution: Enter the RESet primary command without any argument, then resume your editing.

`SER070A` `Command not recognized | Enter Insert, Delete, Repeat, eXclude, Undelete, Show, Move, or Copy.`

Explanation: You have entered an invalid line command.

Solution: Enter one of the listed commands.

`SER071A` `Interface VRM not proper | Proper Version of PAN/LIB interface required; Regen.`

Explanation: An old version of the interface module has been used. The access to PANvalet and LIBrarian master files is performed by the module which must have previously been generated at install time.

Solution: Regenerate, following the instructions in the ChangeMan ZMF Installation Guide.

`SER072I` `"WIS" Saved | Current consolidation effort has been saved in “work in suspense".`

Explanation: The user has issued the SAVE primary command from the Reconcile panel or END [PF3] to exit that panel.

Solution: None is required. You may cancel any reconciliation made after this point, then load the WIS file to reverse the reconciliation to its state prior to that message.

`SER073I` `&BLKPEND Pending | Block command &BLKPEND is pending.`

Explanation: You have entered a valid block command which has not yet been bounded by the other half. &BLKPEND is filled in appropriately with DD, UU, RR, or XX. This message will appear until you bound the block command.

Solution: Complete the pending command or enter the RESet primary command without any argument.

`SER074A` `Command conflict | Block command &BLKPEND is pending; complete it or enter RESet.`

Explanation: You have entered a line command while block command &BLKPEND is still pending.

Solution: Complete the pending command or enter the RESet primary command without any argument.

`SER075A` `Invalid command | Enter “F" or “L", plus a numeric, blank, or "*" on excluded lines.`

Explanation: You have entered an inappropriate command on a line containing “NOT Displayed" marker.

Solution: Enter first or last line command with an argument, if desired.

`SER076A` `Invalid command | “Locate" or “Create" (project) with an up to 8 char argument allowed.`

Explanation: M+R does not recognize the primary command as entered.

Solution: Enter “L" (“Locate") and an argument on the Consolidation Workplace panel, or ignore. Enter “L" (“Locate") or “C" (“Create") and an argument on the Projects panel, or ignore.

`SER077A` `Invalid command | Follow "Locate" or “Begin" with a numeric value from 0 to 999999.`

Explanation: You have entered a non-numeric after a “Locate" or “Begin" command.

Solution: Follow it with a numeric only, e.g., Locate 37, Begin l987.

`SER078A` `Invalid command | Enter “F" or “L", plus a numeric, blank, or "*" on deleted lines.`

Explanation: You have entered an inappropriate command on a line containing a “DELETED" marker.

Solution: Enter First or Last command with an argument, if desired.

`SER079I` `Nowhere to scroll | Nothing on the &ZVERB of the display. Nothing on the LEFT of the display.`

Explanation: You have entered one of the “LEFT" or “RIGHT" scrolling commands. All the content of the records in that direction is entirely displayed.

`SER080A` `Seq no. higher than Base | BEGIN / LOCATE Seq. no. higher than the highest Sequence Number of Base.`

Explanation: You have entered the “Begin" or “Locate" command with a sequence number which is higher than the highest sequence number of the base.

Solution: Repeat the command with lower sequence number.

`SER081A` `Source ID invalid | Requested ID of source derivative does NOT exist — see Header.`

Explanation: You have entered an M+R primary command with an ID for a source code derivative that does not exist.

Solution: Check IDs displayed in the header (the third line) on the Reconcile panel and repeat the command. If there are two IDs per a nickname, the first one is the ID of the source code version and the second is the ID of the copy/include code version.

`SER082I` `Derivative NOT excluded | Nothing to Reset — this Derivative has NOT been eXcluded.`

Explanation: You have entered the RESet command with an ID of a derivative which has not been eXcluded.

`SER083A` `Invalid Cmd Parameter | Parm ALL ("*") is valid for First and Last line commands only.`

Explanation: You have entered the parameter ALL (*) for a line command Insert, Delete, Undelete, Repeat, Show, Move, or Copy.

Solution: Repeat the command with blank or number as a parameter.

`SER084A` `Command conflict | Line command is pending; complete it or enter RESet.`

Explanation: You have entered a First/Last line command on a “Line(s) NOT Displayed" or “Line(s) DELETED" line while another line command is pending.

Solution: Blank out the First/Last command and complete the previously initiated pending command or enter RESet.

`SER085A` `F/L Invalid on This Line | First/Last Cmd valid only on “NOT Displayed" or “DELETED" line.`

Explanation: You have entered the First or Last line command somewhere other than on “Line(s) NOT Displayed" or “Line(s) DELETED" lines.

Solution: Repeat the command on a proper line.

`SER086A` `“U" Invalid on This Line | Undelete command valid only on deleted ("/*") or cut ("<<") lines.`

Explanation: You have entered the Undelete line command somewhere other than on previously deleted records shown as “commented out" (/*) or cut (<<) lines.

Solution: Repeat the command on a previously deleted or cut record.

`SER087I` `BROWSE Only | BROWSE Only — ONLY Scrolling allowed.`

Explanation: You have entered an M+R primary command while browsing the Reconciliation Analysis panel. Only scrolling is allowed.

`SER088A` `Command Conflict | &DESTCMD is within the range of &MCOCMD command; enter RESet command.`

Explanation: You have entered a destination command "@" (“A" or “B") which is within the copied/moved block defined by the command "$$" (“C", “M", “CC", or “MM").

Solution: Enter the RESet primary command without any argument.

`SER089A` `Invalid Command | “O"verlay currently NOT supported; Enter RESet command.`

Explanation: You have entered a destination command “O" (overlay) which is not supported in this release.

Solution: Enter the RESet primary command without any argument.

`SER090I` `Batch Not allowed | Submitting a batch job is disabled on your installation.`

Explanation: You have selected option 4 (BATCH), which was disabled during the installation of M+R.

`SER091A` `Severe error | End the session; Contact local Help desk.`

Solution: No user correction possible. Try to recreate and document the situation before reporting to your local Help desk.

`SER092A` `PQUERY Service error | ISPF PQUERY Service error; Contact local Help desk.`

Explanation: An error was detected on return from an ISPF PQUERY service call.

Solution: No user correction possible. Enter END primary command. Then continue through the option 5 (EDIT) on the Member Reconciliation menu or Select on the Consolidation Workplace panel.

`SER093A` `Nothing to Export | No member has been selected for execution — nothing to Export.`

Explanation: The user has issued the Export line command against a member in the Consolidation Workplace when no member has ever been executed in this M+R session.

Solution: The export request is ignored as no reconciliation work exists. You should Select a member for execution or loading from WIS before trying to export.

`SER094A` `Wrong Member to Export | Choose the previously executed Member for Export.`

Explanation: The user has issued the Export line command against a member in the Consolidation Workplace, which either has never been executed or is not the last one executed.

Solution: Issue the Export line command against the just-reconciled member.

`SER095I` `Wrong Member to Analyze | Choose a previously executed/exported Member for Analysis.`

Explanation: The user has issued the Analyze line command against the member in the Consolidation Workplace that has never been executed.

Solution: Issue the Analyze line command against a member with a status of *Execute, *Reconcl, or **Export, that is, a previously executed member.

`SER096A` `“WIS" incompatible | Used for another set of versions; Cancel/Change in Profile or ignore.`

Explanation: You have changed the base and derivative data sets.

Solution: You can CANcel the Versions panel and change the WIS file on the Profile Data Sets panel. Then you can return to the Versions panel to specify the set of versions to be associated with the new WIS. Conversely, you can ignore this message and have the new set of versions associated with the old WIS file. When you exit from M+R and start a new M+R session, this WIS will be used as an information source. However, it is recommended that a set of version libraries is associated with one set of WIS and export files which are not used with another set of versions.

`SER097A` `Export PDS incompatible | Used for another set of versions; Cancel/Change in Profile or ignore.`

Explanation: You have changed the export PDS data set while your WIS file also is PDS. M+R will not use this export library as an information source when displaying the Consolidation Workplace panel.

Solution: You can Cancel the Versions panel and restore the proper export file on the Profile Data Sets panel. Then you can return to the Versions panel to specify the corresponding set of versions associated with that export PDS. Conversely, you can ignore this message and have the old set of versions associated with the new export file. When you exit from M+R and start a new M+R session, this export file will be used as an information source. However, it is recommended that a set of version libraries is associated with one set of WIS and export files which are not used with another set of versions.

`SER098I` `Nothing to Print | No member has been selected for execution — nothing to Print.`

Explanation: The user has issued Print line command against a member in the Consolidation Workplace when no member has ever been executed in this M+R session.

Solution: Action: The print request is ignored as there is no reconciliation to print. You should either Select a member for execution or load from a previously saved WIS.

`SER099A` `Wrong Member to Print | Choose the previously executed Member for Print of last view.`

Explanation: The user has issued Print line command against a member in the Consolidation Workplace which either has never been executed or is not the last one executed.

Solution: Issued Print line command against the just-reconciled member.

`SER101A` `Invalid Command | "&V03GAS1" is an invalid primary command; Enter HELP for commands.`

Explanation: You have entered an invalid primary command repeated in place of &V03GAS1.

Solution: Review HELP for list of valid primary commands.

`SER102A` `Command Conflict | Unable to execute; Report to local help desk; Enter RESet command.`

Explanation: You have entered an invalid combination of commands which causes the system to prompt you to reset this series of commands and start anew.

Solution: Enter the RESet primary command without any argument.

`SER103I` `Only 2560 lines executed | Only 2560 lines have been moved/copied — stack limit.`

Explanation: The range of a Move/Copy/Repeat command has exceeded the stack limit of 2560 records. Only the first 2560 records have been moved/copied. You may re-issue the command for the rest of the records.

`SER104I` `Already exported | Selected member already exported and will be overlaid on second try.`

Explanation: You have selected a member that had been previously exported. A second attempt to export that member will overlay the previous export.

`SER105A` `Invalid command | Follow “Find" with a string possibly within quotes.`

Explanation: The argument of a Find command has not been entered.

Solution: Enter Find command and a string argument. If the string contains blanks, enclose it with a pair of quotation marks (“) or apostrophes (‘). If the string contains (“), enclose it with (‘), and vice versa. NOTE The search for a string enclosed with a pair of quotation marks or apostrophes is case sensitive.

`SER106A` `Invalid command | Closing quote of “Find" string missing; Please re-enter.`

Explanation: The argument of a Find command has the beginning quotation mark (“) or apostrophe(‘) but the corresponding closing one is missing.

Solution: Re-issue the command with the corresponding closing quotation mark or apostrophe. NOTE The search for a string enclosed with a pair of quotation marks or apostrophes is case sensitive.

`SER107A` `Bottom of Data | Chars NOT found; Press (R)FIND key to continue from Top of Data.`

Explanation: The bottom of the data has been reached without finding next occurrence of the Find command argument.

Solution: Press (R)FIND key to continue the search from the top of the data.

`SER108I` `No such chars | Requested char string NOT found.`

Explanation: The entire data has been searched without finding any occurrence of the Find command argument. If this message appears in response of a Find ALL command, its argument string has not been found in any of the not deleted base/derivative/user-inserted records regardless of whether they are included or excluded into/from the current view. Otherwise, in case of “Find" without the “ALL" argument, its argument string has not been found in the current view data. You may want to issue the Find command again, with the “ALL" argument.

`SER109I` `Nothing to find | (R)FIND Argument has NOT been provided yet.`

Explanation: The R(FIND) key has been pressed without previous Find command. Issue a Find command or ignore.

`SER110I` `Change error | Change aborted due to both strings being equal.`

Explanation: A Change ALL command has been issued with two equal arguments which renders it senseless. The “Change" command is not executed.

`SER111A` `Invalid command | Follow “Change" with two strings possibly within quotes.`

Explanation: A Change command has been issued with none or only one string argument.

Solution: Re-issue the Change command with two string arguments and, if needed, an “ALL" argument, and/or (if needed) with a numeric position for the searched (first) string.

`SER112A` `Invalid command | Closing quote of “Change" string missing; Please re-enter.`

Explanation: An argument of a Change command has the beginning quotation mark (“) or apostrophe(‘) but the corresponding closing one is missing.

Solution: Re-issue the command with the corresponding closing quotation mark or apostrophe. NOTE The search for a string enclosed with a pair of quotation marks or apostrophes is case sensitive.

`SER113I` `Nothing to change | (R)CHANGE Arguments have NOT been provided yet.`

Explanation: The R(CHANGE) key has been pressed without previously pressing the R(FIND) key. Press the (R)FIND key, then the (R)CHANGE key, or ignore.

`SER114I` `Change error | Change aborted due to Max Record Length overflow.`

Explanation: A Change command has been issued which tries to replace a string with one of bigger size causing the Max Record Length to be exceeded. The Change command is not executed.

`SER115I` `&FCOUNTR Records Changed | ALL NNNNNN records changed.`

Explanation: A Change ALL command has completed successfully. &FCOUNTR is the total number of records which have been changed. If a record has contained more than one occurrence of the first string argument of the Change ALL command, all such occurrences have been changed, but the record is counted once only in the &FCOUNTR total.

`SER116I` `Change Error | &FCOUNTR records changed; Max Length overflow for &CCOUNTR records.`

Explanation: A Change ALL command was completed successfully. &FCOUNTR is the total number of records which have been changed. nnnnnn is the total number of records which have not been changed due to exceeding the Max Record Length. If a record has contained more than one occurrence of the first string argument of the Change ALL command, all such occurrences have been changed, but the record is counted once only in the &FCOUNTR total.

`SER117I` `Change error | Max Record Length overflow for ALL &CCOUNTR records.`

Explanation: A Change ALL command was completed unsuccessfully. &CCOUNTR is the total number of records which have not been changed due to exceeding the Max Record Length. For all &CCOUNTR records which contain the first string argument of the Change ALL command, the required change would have exceeded the Max Record Length.

`SER118I` `Change error | Change argument NOT found in any record.`

Explanation: A Change ALL command has completed unsuccessfully. No records containing the first string argument of the Change ALL command have been found. Put String in Quotes | Put quotes (“") around the string of characters to be displayed.

`SER119A` `Put string in quotes | Put quotes (“ ") around the string of characters to be displayed.`

Explanation: At least two numbers specified as arguments of a Find or Change command—one of them should be the position while the other the search string.

Solution: Re-issue the command with quotation marks (“) or apostrophes (‘) around the search string leaving the other number to be the requested position.

`SER120I` `Nothing to Paste | No CUT has been taken during this Reconcile session to Paste.`

Explanation: A PASte command was completed unsuccessfully due to lack of source to paste. No CUT command has been issued during the current Reconcile session. Whenever you issue END or CANcel commands and return to the Member Reconciliation menu or Consolidation Workplace panel, the content of the last CUT command (if any) is lost. Multiple PASte commands can be issued after a single CUT command. Each CUT command overrides the content of a previous such command.

`SER121I` `Base already included | Base records are displayed for the current context (view).`

Explanation: A Reset BAse command has been entered for the current context without a previous command eXclude BAse for that context (view). Base records for the current context (view) are displayed, nothing to reset.

`SER122I` `Base already excluded | Base records are NOT displayed for the current context (view).`

Explanation: Either an eXclude BAse command has been entered for the current context after a previous command eXclude BAse had already been issued for that context (view), or the current context does not contain base records (e.g., View COnflicts or eXclude COnflicts). In either case, base records for the current context (view) are NOT displayed; that is, there is nothing to exclude.

`SER123I File ID already included | Derivative records are displayed for the current context (view).`

Explanation: A REset derivative ID command has been entered for the current context
without a previous eXclude command (for this ID) in that context (view). This means that derivative records for the current context (view) are displayed anyway; there is nothing to reset.

`SER124I` `File ID already excluded | Derivative records are NOT displayed for the current context (view).`

Explanation: Either an eXclude derivative ID command has been entered for the current context after a previous eXclude command for this ID has been issued in that context (view), or the current context does not contain these records (e.g., eXclude ALL). This means that derivative records for the current context (view) are not displayed; that is, there is nothing to eXclude.

`SER125A` `Invalid Position | Specified position exceeds current maximum record length.`

Explanation: The number specified as a required position of the search string is greater than the current maximum record length, that is, the longest record in the base derivatives.

Action: Re-issue the command with a proper position request. Note that the minimum record length on the Reconcile panel is 80 character and the maximum is 240 character.

`SER126` `Project invalid | Project must be alphanumeric starting with alpha, @, #, or $.`

`SER130A` `Invalid Package Level | Package level must be simple or participating.`

Explanation: Displays when a user tries to perform a function on a change package that does not match the package level, such as trying to freeze a super/complex package or trying to update remote site information for a super/complex package.

Solution: Specify a simple or participating package ID.

`SER131A` `No Staging Library | No Staging Libraries found for that package; use another package.`

Explanation: Displays when no Staging libraries are allocated for the requested package. Either they were never allocated, or they were deleted.

Solution: Specify a package ID with existing staging library.

`SER132A` `No Staging Library | Staging Libraries aged for that package; use another package.`

Explanation: Displays when the staging libraries have aged.

Solution: Specify a package ID with existing staging libraries.

`SER133A` `Staging Library Deferred | Check out or stage that component to allocate it.`

Explanation: Displays when a user tries to process a library type that was deferred during package creation. A deferred Staging Library Type can only be allocated when a component of that type is checked out or staged.

Solution: Checkout or stage a component for that staging library.

`SER134A` `Library Type Disallowed | Compare/Merge of like LOD library type is disallowed.`

Explanation: Displays when a user tries to compare and merge a change package library that is a load module type (LOD), and it is not allowed. See the “Comparing Staging Libraries to Baseline/Promotion" chapter in the ChangeMan ZMF User Guide.

Solution: Specify a proper library type for that package ID.

`SER135A` `Internal Reader error | Unable to use internal reader; Submit member @@CDFJOB of your WIS.`

Explanation: Severe error has occurred while submitting a batch job. The job deck is properly formatted and written to your WIS data set as member @@CDFJOB.

Solution: Split the screen, invoke ISPF/PDF Edit, select @@CDFJOB in the current WIS PDS, and submit the job.

`SER136A` `No JOB stmt or TIME parm | First card must contain JOB statement; TIME parameter is mandatory.`

`SER137I` `&MSGSHRT | Batch Job to compare and merge version libraries has been`

submitted.

Explanation: Standard message providing the job name and ID when a batch job is submitted successfully.

`SER138I` `Cannot run in Batch | Unable to submit batch job; WIS must be PDS, RECFM = VB, LRECL > 273.`

Explanation: The WIS in the profile is a SEQuential data set while the Batch Execution is possible only if it is a PDS with proper DCB parameters. If you enter a new DSNAME, M+R will allocate it for you.

`SER139A` `Load Lib DSName unknown | Fill in STEPLIB DD statement and submit member @@CDFJOB of your WIS.`

Explanation: M+R expects to find its load library name from a specific DDNAME depending on the way M+R is installed in your site:

CDFLLIB for M+R as a stand alone product.
CMNLLIB for M+R as an option of ChangeMan ZMF.
CPXLLIB for M+R as an option of Comparex.

In case such a DDNAME is not defined but your ISPF is 4.1 or higher, M+R will call the QLIBDEF service to find the current LinkListed load libraries list and use it in the STEPLIB statement. If your ISPF is 3.x or earlier, M+R will try to find the load libraries list of the ISPLLIB DDNAME for the task and use it in the STEPLIB statement. If the above fails, M+R writes the formatted job deck in your WIS library as a @@CDFJOB member.

Solution: Split the screen, invoke ISPF/PDF Edit, select @@CDFJOB in the current WIS PDS, add the name of the M+R load library in the STEPLIB statement, and submit the job.

`SER140A` `Invalid Export Mask | Export member name mask is invalid; format with "?", "*", "-".`

Explanation: The mask to format the member name of the consolidated version on export is considered invalid. Valid symbols are:

Question (?) mark - denotes any one alphanumeric character at this position.
Asterisk (*) - denotes zero, one, or more alphanumeric characters.
Minus (-) sign - denotes replacement of one or more characters with the following string.

Solution: Enter valid export name mask. For example, if you want to add a suffix ‘2’ to each exported member name, the mask would be “*2". If you want to replace the first character with ‘K’, the mask would be “-K*".

`SER141A` `Invalid Export Name | Invalid member name Length after applying the Export name Mask.`

Explanation: The mask to format the member name of the consolidated version on export is such that, when applied to the exported member name, makes the name too long—more than eight character (ten character for PANvalet library).

Solution: Check whether you have missed the replacement symbol “-". For example, if you have defined the mask “*311", M+R will add three digits after each member name on export. However, the mask “*-311" will replace the last three characters with the three digits.

`SER142A` `WIS incompatible | The WIS belongs to another M+R Tool; use a compatible WIS DSNAME.`

Explanation: The WIS data set entered on the Profile Data Sets panel or through an M+R project has been used to store unfinished work in another M+R tool.

Solution: Change the WIS DSNAME to one used within the current tool.

`SER143I` `Not Member/SEQ Versions | Member Reconciliation requires member of SEQ versions, not library.`

Explanation: The base version that you have entered on the Versions panel (option 1) of the Member Reconciliation tool is a library and you have not specified a member name. The alternative message is SER144I below.

Solution: Specify a member name, or use the Library Consolidation tool.

`SER144I` `Not Library Versions | This M+R Tool requires library versions, not member or SEQ.`

Explanation: The base version that you have entered on the Versions panel (option 1) is not a library—it’s either a specific member or a sequential file. The alternative message is SER143I above.

Solution: Specify a member name pattern, or range, or masks, or use the Member Reconciliation tool.

`SER145A` `Incomplete Installation | Ask System Programmer to provide M+R Projects Data Set as per manual.`

Explanation: The team-oriented Projects and Samples data sets need to be made known to M+R by manually editing the SEROJECT panel in the M+R PANELS library. If these data sets are not allocated with the required parameters, or cannot be opened and read, or the samples data set does not contain the WALKBAS, WALKDV1, and WALKDAV2 members, this message is issued and some functions are not available.

Solution: Ask the system programmer of your site to perform the actions advised in the installation guide:

In the )INIT section of the SEROJECT panel, enter:

&CDFPROJ = somnode.CDF.PROJECTS
&CDFSAMPL = somnode.CDF.SAMPLES

The DSName somnode.CDF.PROJECTS and somnode.CDF.SAMPLES are examples only.

The M+R Projects data set has to be allocated as a SEQuential file, with:

Record Format FB
Logical Record Length 80
Block Size 6000
First extension 20 blocks
Secondary extension 400

All M+R users should be granted READ/WRITE authority to the Projects data set somnode.CDF.PROJECTS.

All M+R users should be granted READ authority to the Samples data set, somnode.CDF.SAMPLES.

`SER146I` `No Projects found | No individual project; not in any team-oriented project.`

Explanation: The user has not created any individual project nor he or she is a team member of any of the team-oriented project in the M+R project data set.

`SER147I` `Project Purged | Successful Purge of the selected project, WIS, Print data sets.`

Explanation: The project that you have selected for purging has been removed from the M+R project data set. Moreover, the WIS and Print data sets associated with that project have been deleted. Also see SER151.

`SER148I` `Project Loaded | Successful Load of the selected project {``name/ownerid``}.`

Explanation: The project NAME/OwnerID that you have selected has been loaded. The profile settings, working data sets, and version data sets have been set accordingly.

`SER149I` `Project Created | Successful Create of the new project {``name/ownerid``}.`

Explanation: Your new project Name/YourID has been created. The updated profile settings and working data sets specified on the Profile panels, as well as the version data sets specified on the Versions panel and Copy Versions panel, have been included in that project.

`SER150I` `Not Authorized | Invalid request against a project - user not authorized.`

Explanation: The action requested can be performed only against a project that you had created. For example, you cannot request project details, delete, or purge a project that is owned by somebody else.

`SER151I` `Project Deleted | Successful deletion of the selected project.`

Explanation: The project that you have selected for deletion has been removed from the M+R project data set. However, the WIS and Print data sets associated with that project have not been deleted. Also see SER147.

`SER152A` `Not unique name/owner | New project name and your logon ID must be an unique combination.`

Explanation: The project that you are trying to create has no unique ID formatted from the project name and your TSO logon ID.

Solution: Change the project name and try again. You can check the list of M+R projects of both the Library Consolidation and Source/Copy Synchronization tools to pick up a unique name. If a project with the same name exists but you are not its owner, you could use that name as desired.

`SER153A` `Invalid Line Command | “S" to load, “F" for details, “U" to update, “D" to delete, “P" to purge.`

Explanation: You have entered an invalid line command.

Solution: Enter one of the listed commands.

`SER154I` `Project Updated | Successful update of the selected project.`

Explanation: The Update line command can be issued against a project or task. Depending on that, there are two results from an Update:

The project you have selected has been updated. The updated profile settings and working data sets specified on the Profile panels, as well as the version data sets specified on the Versions panel and Copy Versions panel, have been included in that project.
The task you have selected has been replaced. If the Member List selector has been used for the selected task, the new members have been added to the task.

`SER155A` `Invalid Complexity | Enter High, Middle, Low, or None for Degree of Complexity.`

Explanation: You have misspelled an assignment of the Degree of Complexity selector. The long message above is the full set of valid values.

Solution: Enter the first letter: H, M, L, or N.

`SER156A` `Invalid Pattern or Mask | Pattern must be alphanumeric ending with “*"; Mask also may have “?".`

Explanation: You have attempted to specify a pattern or masks as a selector for an assignment that contains invalid characters.

Solution: Specify a valid pattern like “ABC*" to select all members whose name starts with the string ‘ABC’. You can also use:

Suffix masks like *1, *2, and *3.

Or position masks ??1*, ??2*, and ??3*.

Or prefix masks X*, Y*, and Z*.

Or any reasonable combination of these types of masks, including all three of them; combining the above examples, the masks should look like X?1*1, Y?2*2, and Z?3*3.

`SER157A` `Duplicate Assignment | Another task already assigned to team member; use Update to change.`

Explanation: You have attempted to assign a task to a team member who already have another task assigned.

Solution: If you want to assign the new task, issue Full details command against the project and then issue Update against the previously assigned task. Now it will be replaced with the new task. Note that if the task selector is Member List, you can delete some members as desired before adding new members through the Update command.

`SER158I` `Task Assignment complete | Successful assignment of the specified task to a team member.`

Explanation: This message acknowledges that the specified task has been assigned to the designated team member (logon ID). You can continue with new assignments to other team members or END to return to the Projects panel.

`SER159I` `Not TeamOriented Project | Selected project is NOT team-oriented; no details.`

Explanation: You have attempted to issue a Full details command against an individual project. Only team-oriented projects may have task assignments that are displayed in response to the Full details command.

`SER160I` `Already in Full view | Selected team-oriented project already displayed in full.`

Explanation: You have attempted to issue Full details command against a team-oriented project that has already been displayed in full detail.

`SER161A` `Invalid Line Command | Use “U" to update, “D" to delete, and “P" to purge.`

Explanation: You have attempted to issue a Select or Full details command against a task (assignment). Only projects may be selected. Only team-oriented projects may have task assignments that are displayed in response to the Full details command.

`SER162I` `Team Task Deleted | Successful deletion of Team Member Task of the selected project.`

Explanation: The task that you have selected for deletion has been removed from the M+R project data set.

`SER163I` `No Purge: Active project | Selected project is now Active, its WIS in use; cannot be Purged.`

Explanation: The project that you have selected for purge is the currently active project. Therefore, the work in suspense (WIS) and Print data sets associated with that project can NOT be deleted. You might try to delete that project as desired.

`SER164A` `Invalid Project | Selected project information is corrupted; delete/recreate.`

Explanation: You have selected a project whose information entry in the M+R project data set is corrupted, possibly due to direct editing of that data set.

Solution: Delete the project from the Projects panel and create it anew.

`SER165A` `Cannot Load Project | Unable to load selected project; “work-in-suspense" (WIS) is not PDS.`

Explanation: You have selected a project whose WIS data set is not PDS, maybe due to direct editing of the M+R project data set.

Solution: Delete the project from the Projects panel and create it anew with a PDS as a WIS data set.

`SER166A` `Invalid Project Data Set | Individual Projects data set is missing or corrupted.`

Explanation: Your M+R project’s data set has been deleted and hasn’t been allocated due to system reasons.

Solution: Exit M+R and invoke it again.

`SER167A` `Cannot Update Project | Cannot update not active project; First Load then Update project.`

Explanation: You have attempted to update a project that is not the current active project.

Solution: Load the project, then update it.

`SER168I` `Invalid Mask Format | All masks must be of same length and type — prefix, suffix, position.`

Explanation: You have specified masks that have different length (for example, *1 and *123) or masks of different type (for example, a prefix mask, ab*, and a suffix mask, *ab). Use masks of one of the following types:

Suffix masks like *1,*2, and *3
Or position masks ??1*, ??2*, and ??3*
Or prefix masks X*, Y*, and Z*
Or any reasonable combination of these types of masks, including all three of them; combining the above examples, the masks should look like X?1*1, Y?2*2, and Z?3*3.

`SER169I` `Last project loaded | Active Project in force; Successful load of {``name/ownerid``}.`

Explanation: The project NAME/OwnerID was the last project you have used in the previous M+R session. It has been loaded on the invocation of the Library Consolidation or Source/Copy Synchronization tool. The profile settings, working data sets, and version data sets have been set accordingly.

`SER170I` `Member @@CDFSET not found | Attempt to load @@CDFSET member of work-in-suspense failed.`

Explanation: The local repository of the project information—member @@CDFSET in the current work in suspense data set—has NOT been found. The profile settings, working data sets, and version data sets have not been updated. You may want to recreate this project.

`SER171I` `Member @@CDFSET corrupted | Member @@CDFSET of work-in-suspense considered corrupted.`

Explanation: The local repository of the project information—member @@CDFSET in the current work in suspense data set—is corrupted, possibly due to direct editing. The profile settings, working data sets, and version data sets have not been updated. You may want to recreate this project.

`SER172A` `Invalid Show Request | Place Show line command on the first cut/pasted line of moved block.`

Explanation: You have entered the Show line command at some code line other than the first cut/pasted line of a “moved around" block of records.

Solution: Re-enter the command on the first cut (<<) base record or pasted (>>) derivative record of a moved block of records.

`SER173A` `Cannot Run in Batch | Unable to execute in batch mode; Export data set must be a library.`

Explanation: The Export data set in the profile is SEQuential while export options have been selected on the Batch Execution panel. You can specify an existing library for export or enter a new export DSNAME on the Profile Data Sets panel for M+R to auto-allocate it as a PDS.