File Manager messages

File Manager does not have enough virtual storage to start or to continue the current function.

You called a File Manager function that cannot be run in batch mode.

You called a function that is not part of File Manager for z/OS®.

You called a File Manager function that cannot be run in full-screen mode.

You called a File Manager function that cannot be run in command mode.

You called a File Manager function that cannot be run in line mode.

You called a File Manager function that is not available.

File Manager is unable to get RACF® information via RACROUTE. For more information, refer to the RACROUTE return and reason codes.

The security exit must exist in LPA.

Your user ID is not authorized to use the function that you specified.

Your user ID is not authorized to use the fullpack disk functions on the specified volser.

You invoked a function that cannot be run in authorized mode.

The volume xxxxxx is too large for fullpack disk functions. Fullpack disk functions are restricted to volumes with total capacity less than 65536 tracks.

The panel cannot be displayed.

The DD name referenced has been closed due to processing of another WRITE function that shares the same tape unit. This file cannot be re-opened once it has been closed.

The requested CICS® I/O request failed against the selected CICS® resource. VSAM returned the listed return code and error code. Additional error messages may have been written to the CICS® or system log.

File Manager was updating the profile and an error occurred.

The File Manager installation or user profile was not found or is in error. The default values supplied by IBM® are used.

An invalid parameter was found in the File Manager installation profile. The default values supplied by IBM® are used.

A syntax error was detected in the File Manager installation profile, in or near the indicated parameter. The job continues using the IBM®-supplied defaults.

A client on a system that supports IPv6 attempted to establish a connection with File Manager but did not pass the required HOSTNAME parameter.

IPV is not at the minimum required service level to interface with your installed version of FM/CICS.

You have issued the load module I command against a control section that does not have any user data stored for it.

You have issued the load module S command against a control section that has no text data for this class.

The SET RECLIMIT processing option specifies a start position that is greater than the record length of the record you are trying to print.

You specified SET PRINTOUT=REXX, but File Manager was not called from a REXX procedure. The print output is routed to SYSPRINT instead. (SET PRINTOUT=SYSPRINT).

You have issued the load module Z command against a control section that has no ZAP data.

The message indicates an error in a control card. A subsequent message contains more information about the error.

You omitted a required parameter.

You either omitted a function code or specified an invalid function code.

The syntax of the control statement is invalid. A scale is printed to help you find the error.

You might have specified excessive or duplicate parameters.

You specified two parameters that cannot be used together.

You did not supply a required parameter.

You did not supply a required parameter.

An expected continuation of the control statement could not be found or contains invalid syntax.

The parameters for the File Manager invocation are terminated by a comma.

The execution of a File Manager external REXX function funcname returned retcode.

A request to use DFSMShsm HRECALL to recall a data set was successful.

A request to use DFSMShsm HRECALL to recall a data set failed. The attempt to run the command using IKJEFTSR gave return code ikjrc, and the command gave return code rc with reason code reason.

You specified an unknown parameter or a parameter that is not applicable for this function.

File Manager cannot determine an abbreviated parameter that you specified.

A value for the specified parameter could not be found.

You supplied a parameter that is not used by this function, or a duplicate parameter.

You specified an incorrect value for a parameter.

You specified an incorrect value for a parameter.

You specified an incorrect value for a parameter.

The key length value and key location value that you specified would result in a key that does not fit into the record where it is to be used.

The key location, plus the key length, minus 1 must be less than or equal to the record length. (For example, if the key location is 50 and the key length is 10, the record length must be 59 or more.)

The increment value does not fit within the key length specified.

You called a function that interprets punched cards, but your card punch cannot interpret cards.

You have issued the load module O command against a control section where the compiler options cannot be determined.

There is no data set available for processing. File Manager cannot process dummy data sets.

The function you tried to use requires the FMNIIPRT DD to be allocated to the same device as SYSPUNCH.

The indicated tape is positioned at the end of the tape (that is, after the end-of-tape (EOT) mark). If the tape is a reel, it might be pulled off the feeding reel.

The indicated tape is positioned at the end of the tape (that is, after the end-of-tape (EOT) mark). If the tape is a reel, it might be pulled off the feeding reel by subsequent forward processing of the tape.

You called the Erase Tape function, but the tape unit cannot perform the Erase Tape function.

An error occurred on the indicated tape unit. If a read data check occurred, message FMNBA163 might follow.

An error was found reading from an input tape.

You specified EOD as the number of files in a tape function, but you have not specified an EOD value with the SET function. There is no default EOD value for tapes.

File Manager could not allocate a buffer large enough for the record.

File Manager could not allocate a buffer large enough for the block.

The end of data on an input tape has been reached. (If a data check occurs immediately after a tape mark, File Manager assumes that the end-of-data has been reached.)

The attribute &ATTR has been specified more than once for element &ELEM at the offset &nn.

Invalid XML - the expected end tag was not specified for element &ELEM.

Invalid XML - an incorrect endtag for the specified element was found.

Invalid XML - data found beyond final end tag.

This message is preceded by other messages that indicate what the severe error was. This is most likely to be an insufficient memory issue.

This is an informational message to display the XML where the error was detected. Its is followed by FMNBA199 which has a vertical bar to the current position the parser was processing when the error occurred.

This informational message follows the FMNBA198 message to indicate the exact location of the error.

You have requested TEXT comparison without the wide listing option. This is an informational message to say the listing option has been changed to accommodate TEXT comparison.

This is an informational message produced by the view load module utility to document the number of control sections that were found.

This is an informational message produced by the view load module utility. The message documents the summary information on the load module only and no details of CSECTs because the summary option has been selected.

The specified disk record does not exist on this track.

A home address record was not found at the specified disk location. This is probably a hardware error.

The DRL function lets you change an end-of-file record into a record that has a KEY and DATA field (convert EOF to a data record).

Either an attribute value or the data value for the specified element are invalid.

A CDATA tag has been provided but no end CDATA string was found.

The element specified is a child element, but has been specified with the wrong parent element.

A required element has not been specified.

A <member lib="&no" ...> value has been specified where the library number exceeds the number of <library>data set name </library> value provided previously.

The attribute value specified is invalid for the current element.

During template editing an update was requested by providing the <copybooks> ... </copybooks> tags. The copybooks provided deleted fields that were referenced previously in criteria in the template and the template cannot be updated without this criteria information being lost.

The <layout> id attribute is either missing or the value specified is not a valid 01 symbol reference number in the template.

The related01 attribute specifies a value that is not a valid 01 symbol reference number in the template for related ID. A related 01 must be a symbol reference of an 01 layout other than the current layout.

The <criteria > tag has been specified without the required type attribute or the type attribute does not specify one of the following values: ID, RID or SEL.

The <criteria > tag must specify byfield="1" attribute value for a dynamic template.

The <criteria> tag must specify type="SEL". Any other type value is invalid.

The specified expression causes the template segment block to exceed the maximum allowed 32760 bytes.

The specified expression is invalid. The offset provided is the byte location into the expression where the error was detected.

The reference number specified on the <symbol> tag is invalid for the current layout. Must be a number in the range shown in the message.

When you are creating a dynamic template the symbols references must be provided in sequence starting from 2.

When you are creating a dynamic template the start attribute must be specified.

When you are creating a dynamic template the start attribute value cannot be zero for non offset start values.

When you are creating a dynamic template the type attribute must be one of these values:

C

Alphanumeric

AN

Alphanumeric

AX

Alphanumeric displayed in long hexadecimal

VC

Varying character

ZC

Varying character null terminated

B

Binary

BI

Binary

P

Packed decimal

PD

Packed decimal

ZD

Zoned decimal

FE

External floating point

FP

Internal floating point

BT

Bit string

VB

Varying bit

G

Graphic string

VG

Varying graphic

The output tape is not positioned correctly to write a labeled data set. Valid positions are the load point and after another labeled file.

The tape indicated is not a standard label tape, or is not positioned correctly.

The output continuation volume is not a standard label tape.

The <heading> value cannot exceed 20 bytes in length.

The <createn> value should not be specified for the current symbol because its not numeric.

The value specified for the element exceeds the allowable length for this element.

The element specified in the following FMNBA230 message cannot be specified here because it is dependant on specific attributes being set in a parent or it has exceeded the allowed occurrence number for this element. Here is a list of possible problems:

Template <scramble> specifications

• <translate> has been specified without <scramble type="3"> being specified.
• <range> has been specified and conflicts with <scramble> type or a dsn attribute.
• <value> has been specified and conflicts with the <scramble> type or previous <range> specification.
• <sval> has been specified when a value list is not expected. Normally indicates a <scramble> dsn attribute was specified.

Editor <hex> specification

• <hex> tag has been specified more than once.

The element requires certain attributes to be specified as documented in the associated schema:

• <translate> has been specified without incol, outcol or dsn attributes.
• <range> has been specified without min or max attributes.

<scramble type="3"> has been specified and a <translate> element is then expected to specify the translate options. The <translate> element has not been specified.

A <byline> element requires <criteria byfield="1"> and this has not been specified on the parent <criteria> element.

Too many <describe> elements have been specified.

A <describe> or <layout> element is being processed for a non-dynamic template and the TMPX session was invoked without a template.

You have specified the <copybooks> element for a non-copybook or dynamic template.

A <criteria > element has been specified incorrectly. The type="RID" attribute must be specified if a related01 attribute has been specified.

The element value as described in the following FMNBA230 message exceeds the maximum occurrences allowed for this element. See relevant schema.

Either the element value or a required child element has not been specified. This is issued for the <replace> element when either <repfrom> or <repto> are missing, or when <repfrom> or <repto> element is specified without any data.

The volume loaded for input to the EVC (copy) or EVL (list) function is not a valid Exported Stacked Volume. Either the volume has been corrupted or the wrong volume has been requested. Processing cannot continue.

The volume loaded for input to the EVC (copy) or EVL (list) function has a corrupted Table of Contents. Processing cannot continue.

The volume loaded for input to the EVC (copy) or EVL (list) function does not contain the requested logical volume in its Table of Contents. Processing continues.

A duplicate logical volume name has been entered into the logical volume request list. Processing does not continue.

Output volume is not long enough to contain the logical volume being copied. This is a report line (not a message number) for the EVL list function.

The specified device has a type which cannot be used in the function you invoked. (For example, the input device for a disk function is a tape unit.)

No data set dsname was found on the unit specified, or in the VSAM catalog used.

ddname is a ddname referred by an INPUT or OUTPUT parameter, or any other ddname used by File Manager. Either the corresponding DD statement is missing, or the ddname was used and freed by a TLT function.

You invoked a disk update function for a data set already in use by another task.

A dynamic allocation request was rejected by your system's SVC99 validation routine. This is probably due to a restriction imposed by your system.

The data set or tape specified by ddname could not be opened.

The function that you specified cannot be used with the data set that you specified. For example, a VSAM function cannot process a sequential data set.

The indicated operation failed for the indicated data set.

The indicated operation failed for the indicated data set.

By default, report output is written to SYSPRINT. Sections of the output can be directed instead to the following ddnames:

FMNROPT

File Manager active options

FMNRPRM

$$FILEM command parameters and return codes

FMNRPRC

REXX procedure statements read from SYSIN

FMNREPT

Command reports and return codes

FMNRSUM

TALLY summary report

If FMNPRINT is present in the JCL, it is used instead of SYSPRINT.

File Manager requires SYSPRINT to be allocated if alternate ddnames are not specified.

An ABEND occurred during EOV processing for the indicated tape.

The first function that was used on the tape volume required standard label processing, but the function you are trying to use requires non-standard label processing. The tape volume must be reallocated for non-standard label processing.

The tape volume was allocated for standard label output processing, but the function you tried to use requires non-standard label processing.

An unexpected return code was returned for a read or write operation (where hhhhhhhh is the ECB value for the associated operation).

This is probably a hardware error.

A block of the input/output data set does not correspond to the data set's format description from the VTOC or DD statement.

The block size of a fixed unblocked data set must be the same as the record size.

An input block or record has a length that is not equal to, or a multiple of, the output record size.

For a QSAM output function, you specified a block size greater than the maximum supported value.

A block consists of one or more records. The block size must be the same as the record size, or a multiple of the record size.

The record size encountered is not compatible with the output specifications.

The record size encountered is not compatible with the input specifications.

While reading variable-length (blocked) input, File Manager found a data block whose record-length field contains either zero or a number greater than the physical length of the data block.

The indicated REXX variable does not contain a string, or is not defined.

The indicated REXX variable does not contain a valid number, or is not defined.

The indicated block does not contain variable format data, or the value in the block descriptor field is different from the physical length of the data block.

The indicated block does not contain variable format data, or the value in a record descriptor field is invalid for deblocking.

The indicated block contains a segment of a variable spanned record which cannot be assembled to an entire record.

You cannot specify a key position with control interval access or a NONINDEXED VSAM input.

You are using the TV function with the nfiles parameter, to copy more than one tape data set to a single VSAM data set. The output VSAM data set must be an entry-sequenced data set.

You have copied records from one VSAM key-sequenced data set to another VSAM key-sequenced data set. The output data set has a different key position or key length than the input data set.

A VSAM macro returned with an unexpected code. The message includes the failing macro, the return and error codes, and, for some errors, an additional explanation. For more information, refer to the documentation of your current release of VSAM.

yyy might present additional information about the error.

Catalog management returned these return and reason codes as a result of a catalog error or exceptional condition. For an explanation of these codes, refer to the documentation of the system message IDC3009I. If the error is related to a single catalog entry, the defective entry is flagged in the SCS output and the function continues.

VSAM OPEN returned a warning code indicated in the message. File Manager lets you decide whether to ignore the condition or to exit from the function. For more information, refer to the documentation of your current release of VSAM.

VSAM OPEN returned a warning condition. The reason code is documented in manual DFSMS Macro Instructions for Data Sets. File Manager attempts to continue processing.

X'4C' previously interrupted
X'60' data set flagged unusable
X'64' Alternate index not built
X'68' time stamp mismatch
X'6C' time stamp mismatch
X'74' not properly closed

VSAM rejected the RBA you entered. An attempt to locate the first record with a higher RBA also failed.

A VSAM SHOWCAT macro failed (giving return code rc) while searching for information about the specified data set. For an explanation of these codes, refer to the documentation for your current release of VSAM. If the SHOWCAT macro failed for a VSAM alternate index operation, it might show incorrect return codes because of VSAM recovery action.

A data-in-virtual macro has failed. The message includes the type of macro request and the reason code. For an explanation of the return code and reason code, refer to the documentation for your current release of your z/OS® system.

The tape that the operator mounted is not the volume requested.

Standard label output was specified, but the named tape volume is not labeled. The system waits for a reply.

The expiration date on the volume mounted as the output tape was not reached. The system waits for a reply.

The unit unit is not ready. The system waits for a reply.

A manual operator intervention occurred on the indicated unit. The system waits for a reply.

You are running a procedure with *FASTREXX ON specified and the procedure has failed FASTREXX syntax checking for the statement beginning at the line number specified. For continued statements the line number represents the first line for the statement. The column position is the position into the continued statement as printed. This message will be preceded by more detailed messages.

You are running a procedure with *FASTREXX ON specified and the procedure has failed FASTREXX syntax checking when processing the keyword referenced.

This message is used to print the procedure statement (including continuations) that was being processed when the syntax error occurred, or to list the expected keywords when a keyword is processed that is not expected.

This message indicates the keyword being processed is not expected and is followed by a list of expected keywords.

A FASTREXX function has been coded incorrectly - a right parenthesis is missing.

A FASTREXX condition is incomplete - either the left hand side is expected or the right hand side has not been specified.

A DO or SELECT statement does not have a matching END statement.

A REXX comment is incomplete.

A comma has been coded as the last non blank character in the procedure.

A conditional statement has unbalanced left and right parenthesis.

The specified operator is not an operator that has is supported for FASTREXX processing.

The keyword is either a REXX keyword or external function that is not supported for FASTREXX processing.

The runtime control blocks for a Template have been corrupted and an expression that relies on them cannot be run.

FMNRXFUN load module is not the same level or version as the FMNMAIN load module.

FMNRXFUN load module is not the same level or version as the FMNMAIN load module.

The specified function failed with the specified return code. This is normally a problem with the parameters passed to the function.

A SIGNAL statement has been coded without a label value.

This is an internal error that occurs running with a template. The internal function generated for the template expression is incorrect.

Informational message to say the indicated condition is always true.

Informational message to say the indicated condition is always false.

You have specified a constant for a condition and only a 0 or 1 maybe specified..

This message may be produced when listing the expected keywords for message FMNBA423. It indicates that a field reference (#nn) is an allowed keyword.

A signal statement has referenced a label name that has not been coded in the procedure.

The procedure is made up of non executable instructions and therefore cannot be run.

The SIGNAL &label causes an infinite loop because the specified label is the label for the SIGNAL instruction.

This message may be produced when listing the expected keywords for message FMNBA423. It indicates that a numeric or character literal is an allowed keyword.

This message may be produced when listing the expected keywords for message FMNBA423. It indicates that a File Manager external function is an allowed keyword.

DFHXCIS module cannot be loaded via an OS load service. Generally this means the cicshlq.SDFHEXCI has not been included in the TASKLIB, STEPLIB, or LINKLIST for the current File Manager function.

File Manager has attempted to access a CICS® region using the external CICS® interface and has failed to perform the function &FUNC with the response code and reason codes shown in the message. This is normally indicative of a setup problem

File Manager has attempted to access a CICS® region using the external CICS® interface and has failed to perform the a DPL CICS® Link to the FMN3CICS program with the responses documented in the message. This would normally be a setup problem.

File Manager has attempted been unable to start a server task in the CICS® region requested.

A UNIX™ System Service BPX1SOC to create a TCPIP socket has failed with the reason codes specified.

A UNIX™ System Service BPX1CON to connect a socket to the CICS® region server task has failed with the reason codes specified.

A UNIX™ System Service BPX1SND has failed to send data to the CICS® region for the reason code specified.

A UNIX™ System Service BPX1RCV has failed to receive data to the CICS® region for the reason code specified.

A UNIX™ System Service BPX1SND has failed to send the logoff command to the CICS® region for the reason code specified.

A UNIX™ System Service BPX1CLO has failed to close a socket that had been established with the CICS® region for the reason code specified.

File Manager has tried to initiate the FM transaction as a background server task in the specified CICS® system and the started task has either failed to respond within 25 seconds or has not been able to obtain a TCPIP PORT number to be used for the communications that follow.

This message is preceded by FMNBA454 and contains the error message encountered by the server task during initialization processing.

A UNIX™ System Service BPX1GAI has failed to get the address information using the PORT and host name provided by the CICS® region. A connection to the CICS® region cannot be performed.

A generic or blank CICS® APPLID has been entered in the data set name field for a function that will attempt to produce a selection list of CICS® APPLIDs from the FMNCICS DD and the FMNCICS DD has not been allocated to the session.

The data set identified by the FMNCICS DD statement does not have a logical record length of 80 or is not fixed blocked.

FMNCICS DD refers to a PDS or PDSE and a member name has not been specified.

FMNCICS DD refers to an empty data set or member, so no generic selection list can be produced.

You are running a File Manager function in batch or keyword mode and it references a remote resource. File Manager requires the authentication data set that contains the remote definition allocated to the DD name FMNAUTH.

A File Manager function is being processed that references a remote resource and the authentication file (DD FMNAUTH) points to a data set with invalid attributes. &recl is the minimum logical record length allowed.

A File Manager function is being processed that references a remote resource and the authentication file (DD FMNAUTH) points to a partitioned data set and a member name has not been provided with the data set name.

The authentication file contains invalid information. This may have been caused by editing the authentication file outside of File Manager or an internal error during File Manager processing.

The authentication file contains invalid information. This may have been caused by editing the authentication file outside of File Manager or an internal error during File Manager processing.

A list of remote system has been presented and no selection has been made.

The remote system processing produced messages which will be displayed after this message.

The remote system processing produced messages which will be displayed after this message.

This indicates that another task in the address space has a signal handler and File Manager will not be able to initialize a Language Environment® with POSIX(ON) which is required for the session to perform communications with a remote system.

You are running a File Manager function that references a remote resource. An error occurred when creating a socket to connect to a remote File Manager, which may be one of:

• Permission to create a socket of the specified type or protocol is denied.
• Resource temporarily unavailable.
• There has been a network or transport failure.
• Insufficient system resources are available to complete the call.
• There was no NETWORK statement in the parmlib member to match the AF_INET domain.

The named peer could not be resolved to an IP address.

When attempting to connect to a remote File Manager, the intended peer would not connect.

This message indicates that the remote address and port were contactable, however the response was not recognized. This can occur if the port specified is not that of a common server, or if the common server was stopping while attempting to connect to it.

This message indicates the handshake between this machine and the target remote system did not complete.

The remote system server did not respond to the attempt to signon. This indicates an error with the remote system.

The remote system server is not configured with an FM entry.

The password given is not valid for the given user ID on the remote system.

The remote server did not recognize a parameter while signing on. This indicates a configuration or level problem in the remote server.

The remote server encountered a setup issue when attempting to process the user signon. Most likely the remote server is not running from a program controlled library.

The password for the specified user ID on the remote server is expired.

Check the password rules for the target system and respecify the new password.

The target server has an authorisation problem and is not permitted to process the request.

The user ID specified is not known by the target system.

The user ID was refused. Most likely it is revoked on the target system.

The user ID was refused.

An error occurred invoking client.

A nonzero reason code has been returned from the IEFSSREQ service function SSOBSSMS. The reason code is documented in the IBM-supplied IEFSSSA macro.

File Manager failed to connect to Db2®. The indicated Call Attach Facility request did not complete successfully.

A subsystem request to retrieve OAM storage group information from SMS failed with an unexpected return code.

File Manager failed to establish connection with OAM.

The requested OAM function failed.

The requested OAM function failed. File Manager could not access Db2®.

Your user ID is not authorized to access the object directory tables as required.

The requested OAM function failed. An unexpected return code was received from SQL.

An OSREQ STORE request failed because the target collection could not be found, or the user is not authorized to define a new one.

The requested OAM function failed with an SQL return code indicating a locked Db2® resource. This is an information message only. File Manager continues and reissues the SQL request.

The requested OAM function failed with an SQL return code indicating a locked Db2® resource.

You asked to skip more bytes than the object contains. You have effectively asked File Manager not to print any data.

The input data did not contain object header records, thus no defaults for collection and object name are available.

An OSREQ STORE has completed, but it could not use the Storage Class or Management Class that you specified. Default values for the collection were used instead.

An input record was found with unexpected contents, or end of input occurred before the end of an object.

Backup of one or more objects failed. File Manager issues this message at the end of the function. Message FMNBA200 shows the OAM error information for each failing object.

A request to use DFSMShsm HMIGRATE to migrate a data set was successful.

A request to use DFSMShsm HMIGRATE to migrate a data set failed. The attempt to run the command using IKJEFTSR gave return code ikjrc, and the command gave return code rc with reason code reason.

The format of the indicated double-byte character set field is incorrect. File Manager found a double-byte field that has an odd length.

File Manager issues this message for only the first incorrect field it finds. It prints this message at the end of the record, and replaces the last character with an EBCDIC blank (X'40'). The function continues.

The double-byte character set (DBCS) subfield, at the offset shown, was not reset at the end of a mixed DBCS and EBCDIC field. For example, there might be no shift in (X'0F') character marking the end of a double-byte field in mixed DBCS and EBCDIC data.

File Manager issues this message for only the first incorrect field it finds. It prints this message at the end of the record. The function continues.

File Manager has detected incorrect double-byte character set fields in one or more records.

File Manager prints this message at the end of the listing. It indicates that File Manager issued one or more error messages. The function continues.

To run File Manager for z/OS® V14R1, you need z/OS®.

To run File Manager for z/OS® , you need MVS/DFP Version 3 Release 3 or later.

File Manager cannot find a module which is required for your File Manager invocation. This module might have been deleted or protected (for example, if the functions supported by this module are not needed at your installation).

An ABEND occurred while File Manager was running. Depending on the circumstances, a dump might be produced.

File Manager encountered an internal problem. The error is identified by the File Manager error code.

An abend occurred while File Manager was running. code is the z/OS® abend code; reason contains additional information that is available for some cancel codes and abend codes.

An attempt to load the specified module failed with an unexpected error. nnnn-nnn is the z/OS® ABEND and REASON code.

During an attempt to establish connection with the REXX variable pool system services failed.

During an attempt to read from or write to the REXX variable pool the REXX system interface returned an unexpected result.

An unrecoverable I/O error occurred on the indicated device.

This is issued when the XML input is not on a sequential data set or not a member in PDS or PDSE. The data set organization is not supported.

Either the <layout name='value'> or the <criteria rname='value'> have referred to a field name that cannot be matched to an 01 layout name in the current template.

The copybook attribute of the <layout> element refers to a 1 - 8 byte copybook member name. This member must be a valid copybook that was used to build the template. The <layout copybook='&CPY'> can only be repeated for the number of 01s in the referenced copybook. You have either specified a copybook name that isn't referenced in this template or you have repeated the definition more times than the number of 01 layouts referenced in this copybook.

The name attribute value specifies a field name that cannot be located in the current template.

You have specified either an output member mask or not specified an output member name when the input data set is sequential or you have specified an output sequential file without a blank or generic input member name.

Successful completion of an export function.

Statistical summary message for export template function

Statistical summary message for export template function

Statistical summary message for import template function

Statistical summary message for import template function

The indicated SVC99 (allocation) operation failed. The failure occurred during SMS processing.

The indicated SVC99 (allocation) operation failed.

Unexpected return code from the LOCATE macro.

An error occurred while scanning the z/OS® control block TIOT. This is probably a File Manager error.

Unexpected return code when reading the DSCB or JFCB.

A UCB scan operation (to determine the device) failed with an unexpected return code.

An unexpected return code was received from the TSO Service Facility. The TSO command was not executed.

Successful completion of an import function.

This message provides the line number and line offset where the XML error occurred.

This message provides the line number where the XML error occurred.

This message displays the line where the XML error occurred.

You cannot create or update an IMS™ template view or criteria set when running the import function under the File Manager Base component. It must be run from the FM/IMS template options if running in full screen mode or using the program FMNIMS for batch processing.

You are trying to import a template from XML with REPLACE=NO meaning the XML is used to update the existing template. The existing template is as different type to the XML template being imported.

The XML element is repeated more than the allowed number of occurrences for that element.

The element is not valid for the type of template being processed.

You are trying to import a IMS™ template from XML and you have not provided copybook definitions to describe all the segments defined to the corresponding data base.

The associated template data set for a view or criteria set import is not a PDS or PDSE. This could have been specified using the <imstp>data set name</imstp> element. The data set name may also be obtained from the existing view or criteria set for REPLACE=NO, or the existing template definitions for FM/IMS found either on the panels or in the options module definition.

The associated template member for a view or criteria set cannot be found in the current template libraries. The template member name is obtained from the <dbd>name</dbd> definition or for REPLACE=NO can be obtained from the existing view or criteria set definition.

The associated template member for a view or criteria set cannot be loaded because it contains invalid data for a File Manager/IMS template.

The import routine cannot create the template for one of the following reasons.

• The template is a BASE or IMS™ template and <copybook> elements have not been supplied to create the template.
• The template is a Db2® template and <db2object> element has not been provided.
• The template is an IMS™ view or criteria and <imstp> and <dbd> elements have not been provided.
• The template you are trying to import is an IMS™ extract template - this type of template can only be updated. REPLACE=NO must be specified and the template must exist.

The attribute specified is not allowed for the type of template being processed.

You are trying to create a FM/IMS view or criteria set and you have not specified <dbd>name</dbd> which is required to create a view or criteria set.

The File Manager Find/Change utility could not change one or more strings because:

• The change string is longer than the find string and there is insufficient space in the record to accommodate the change string.
• An attempt is being made to change a VSAM KSDS key field, The key field will be identified with a 'K' next to the record number in the report.

• The data set name could not be determined because there is no FMN4POPT REPOS definition or SYS1.PARMLIB definition or TPREPOS DD statement allocated.
• The data set name defined in the FMN4POPT REPOS keyword does not exist.
• You exited the VSAM Define dialog without saving the template repository data set.

The layout specified does not map the key area of the record. Therefore a formatted key cannot be displayed.

The name you entered as a filter did not match any of the layouts in the current template.

The user has exited the 01 Layout List Panel without selecting a layout. The FKEY command processing is terminated.

Formatted key processing requires a copybook or template to be provided to the edit, view or browse function.

You cannot use a picture string with numeric, bit, or Unicode fields.

CICS® returned a non-zero condition after attempting to perform the listed function against the selected CICS® resource.

Errors were encountered that caused File Manager to terminate.

The To template has existing mapping and at least one of the fields it has been previously mapped to cannot be found in the from template. This indicates that the TO template has been either mapped to a different from template, or the from template has changed so that fields previously mapped cannot be found.

File Manager, after being launched from the ADFzCC server, detected that it is not running APF authorized, which is required.

File Manager is shutting down. This message is issued after FMNBB537.

The template does not correctly describe the data for field FLD. Processing is terminated. This occurs when the template describes a record with length LEN1 but a record read from a data set (described by the template) has a record length LEN2, LEN2 < LEN1.

A CREATE, REPLACE, SAVEAS command has been attempted to a CICS® file resource These commands are not supported.

Option 3.6 or FCH batch with the JCL option is being run against a CICS® resource. The option is not supported.

A FACILITY class profile FMNMQ.DISABLE.system_name has been defined, and the current user ID has at least READ access. The result is that all File Manager MQ processing is disabled for this user ID.

The template default for leading zeros is set to YES, so all applicable numeric fields are formatted with leading zeros when printing or viewing data with this template.

The template default for leading zeros is set to NO, so all applicable numeric fields are formatted without leading zeros when printing or viewing data with this template.

The template with the name &MEMBER has been locked.

The template with the name &MEMBER has been unlocked.

After the failure of a z/OS® UNIX™ System Services call, this lists the return value, return code, and reason code.

The output format specified for the date/time field is not a valid picture string for the z/OS® Language Environment® date and time services.

The format used to store the date/time value in the field is required.

The data type for a date/time field must be binary, floating point, packed decimal, zoned decimal, or alphanumeric.

The length of the user defined internal date/time format cannot be longer than the length of the alphanumeric field.

The user defined internal date/time format specified is not a valid picture string for the z/OS® Language Environment® date and time services.

STCK or STCKE was specified as the internal format for the date and time field but the data type for the field is not character or binary.

Date and time fields with an internal format of STCK or STCKE must have a length of either 8 or 16 bytes respectively in order to store TOD clock or extended TOD clock values.

The internal format mask parameter must be specified on the call to the CMP_DATE or CMP_TIME functions when there is no internal date/time format defined for the field in the template.

The output format mask parameter must be specified on the call to the CMP_DATE or CMP_TIME functions when there is no date/time output format defined for the field in the template.

While attempting to build a qualified, unique field name to pass to the CMP_DATE or CMP_TIME functions, File Manager found the name would be greater than 255 bytes.

z/OS® Language Environment® date and time services were unable to convert the field value to a Lilian seconds value.

z/OS® Language Environment® date and time services were unable to convert the field value from Lilian seconds to Lilian days.

z/OS® Language Environment® date and time services were unable to convert the field value from Lilian days to Lilian seconds.

A base date must be provided if day, month, or year adjustment values have been specified.

The format used to display the date/time value is required.

If scrambling is required for the date/time field then a start value for the scrambling range must be provided.

If scrambling is required for the date/time field then an end value for the scrambling range must be provided.

The create base date, scrambling range start date, and scrambling range end date must be valid dates specified in the output format defined for the date/time field.

During copy processing, creation or scrambling of a date/time value failed.

When specifying scrambling options for a date/time field, the range start date/time must be before the range end value.

For XML for a date/time field, the scrtype (scrambling type) value must be RANDOM or REPEAT.

The field specified on a call to the STATS function is not defined as a numeric field in the template.

File Manager could not initialize the ODPP framework so the ODPP API is unavailable for scrambling the field name referenced.

This should not occur and indicates the template is corrupt.

File Manager could not initialize the ODPP framework so the ODPP API is unavailable.

If the date mask is the internal data mask then the field name specified is not able to support that mask. The most common cause would be its length isn't sufficient to contain the mask. If the date mask is the output date mask then it may be incompatible with the internal date mask.

File Manager has detected that the FMNOPTS DD statement is allocated to name, where name is either the name of the data set allocated to FMNOPTS, or "SYSIN" indicating that the FMNOPTS statements have been provided instream. A listing of the options read from FMNOPTS follows.

File Manager has encountered one or more errors while processing the options file allocated to the FMNOPTS DD statement. This message is preceded on one more error messages describing the error(s) encountered.

File Manager has been unable initialize the ODPP framework. The ODPP API returned the message above.

File Manager has been unable to initialize the ODPP framework. The ODPP API returned the message above.

There was a problem opening or reading data from the ODPP license key file.

File Manager has been unable to initialize the ODPP framework. The ODPP API returned the message above.

File Manager has been unable to initialize the ODPP framework. The ODPP API return code is not known to File Manager.

This is an informational message produced after the delete line command has been processed on an enhanced search index member.

This is an informational message produced after the rename line command has been processed on an enhanced search index member.

This is an informational message produced after a find command has been issued from the enhanced search index list. If you place your cursor on a member name, it will be selected to become the target index member for the enhanced search operation. Press Enter on a hit line to navigate to the member in a view session positioned at that line.

This is an informational message produced after the delete line command has been processed on a history command list.

The deletion failed because the command history table is used by another session.

The member name that you try to insert already exists as an index member.

You have specified a search string but not a replace string with the enhanced change panel.

This is an informational message produced after the delete line command has been processed on an history command list.

The enhanced change requires both search and replace strings.

This is an informational statistical message for the enhanced search to summarize the results.

This is an informational statistical message produced after enhanced change command is successfully issued.

The enhanced change command failed with the return code &rc.

The current cursor positioned field has an invalid data set name, qualifier, or name.

An invalid partitioned member name has been specified.

The name of the output data set can only have generic characters where there is a corresponding input qualifier to derive the generic value from.

The input data set prefix or name and output data set name or prefix result in the same input and output data set – which is invalid for the copy process.

The clone process has generated a duplicate output data set name for different input data set names.

The output prefix value &mask is invalid because it does not have a corresponding input qualifier.

The output data set name exceeded 44 characters. This occurs if the output prefix or a suffix to the input data set is too long.

The prefix that is provided does not match any cataloged data sets on the system.

The FMNSREF exec was called with an invalid parameter value.

The FMNSREF exec was called with an invalid function value &function.

The FMNSREF exec was called with an invalid function value &function.

You tried to convert a report to an enhanced search report format, but the report being edited is not a valid enhanced search report. This happens when you edit or view a data set or spool file and the REPORT command is entered with the enhanced search function key.

The enhanced search command detected an invalid parameter in the command string &parm_value.

This is an informational message. This message is issued when a report produced with the File Manager enhanced search batch option was successfully converted to the format required for enhanced search navigation.

An AND (&) or an OR (|) operator is put at the end of a search command string. This is an invalid command syntax. The operator must be followed by a search string.

When you enter a column range, the TO value must be greater than or equal to the FROM value.

The DD name that you entered is invalid. The ddname is 1 - 8 alphanumeric or national ($, #, @) characters or generic characters (*, %). The first character must be alphabetic or national ($, #, @) or generic characters (*,%).

This message is produced with a template save panel where an alternate data set and member name can be provided to save the changes made during template edit.

The template member &MEMBER is a locked template and therefore cannot be changed unless it is unlocked.

The SAVEREF command was issued for a function or panel where it is not supported. For a list of the supported functions, see the File Manager User's Guide.

The GETREF command was issued for a function or panel where it is not supported. For a list of the supported functions, see the File Manager User's Guide.

A GETREF command is being issued an the SAVEREF command was not issued for the current function or panel with the current profile or FMNREFTB allocation.

The GETREF command was issued with a reference name that does not exist.

The SAVEREF command was issued successfully for the &name value.

The SAVEREF command was cancelled after the replace warning was issued.

The GETREF command was successfully issued to retrieve all the field values that are saved with the reference &name.

The SAVEREF command replaced the reference &name with the current values.

The rename panel for a function or panel reference has the same name for the old and new name values.

The new name field on the rename reference name panel has the name of an existing reference.

The data set that is allocated to the FMNREFTB for saving the function and panel reference table has invalid attributes. It must be partitioned and fixed blocked with a logical record length of 80.

The File Manager template is invalid. It may have been corrupted by editing it outside of File Manager.

When File Manager invokes COBOL compiler V5 or later, it may terminate with a Language Environment® abend code. If the abend code is 4093 and reason code X'1C' or 28, there is insufficient storage to run the compiler.

COBOL V5 requires at least 100MB of storage.

While processing the $$FILEM parameters, File Manager encountered errors that caused keyword verification to stop.

File Manager tried to allocate a z/OS® data set. The volume was not available because the associated device was offline.

PDSE data sets are not supported for the Disk Browse, Disk Edit, Disk Print, or Disk Record Scan Utilities.

The z/OS® Language Environment® CEEPIPI failed to load the specified User Exit.

A function specified a starting position whose value is higher than that of the last record on the file. The starting position type might be KEY, RBA, or record number.

This message is issued when a Db2® object name - other than a table - is entered when preparing a Db2® LOAD or UNLOAD utility job. The Db2® LOAD and UNLOAD utilities support only table objects - not views, aliases, synonyms etc.

The Find/Change utility has terminated with a nonzero return code.

File Manager is set up to write audit records to SMF for the current function. A failure occurred while attempting to write an audit record to SMF. The BPX1SMF call resulted in return code &rc and reason code &RSN, both expressed in decimal. The current function may be terminated.

The specified CCSID is not known by this z/OS® system.

The CCSID column is not displayed in single formatting.

The CCSID column is displayed in single formatting.

When the FMAP command has been entered the cursor is not positioned on a selected record or the record at the top of screen is not a selected record.

The field to be mapped has not been selected on the Field Selection List panel.

The template to be used to map the field has not been provided.

The template being used to map the field is larger than the field and data may be truncated.

The column to be mapped has not been selected on the Field Selection List panel.

The field reference specified in the FMAP command cannot be found in the current template.

The data is displayed in the CCSID of the terminal, but is stored internally in Unicode. After conversion to Unicode there are not enough characters to pad the field with Unicode spaces.

The receiving field name is not large enough to hold the converted Unicode field of length lllll.

The routine CNVLCNV could not convert the field name.

The command is not able to be used for a migrated data set.

The user entered a LOCATE command with a field number and character position. The command is invalid because either the specified field is not a character field, or the length of the specified field is 50 bytes or less.

The user entered a LOCATE command with a field number and character position. The command is invalid because the specified character position is greater than the maximum number of characters in the field.

The user entered the CHARPOS editor primary command when the display mode was not SINGLE (SNGL). The CHARPOS command is only valid in SNGL display format. The command cannot be processed.

The user entered the CHARPOS editor primary command. The character position information has been turned off.

The user entered the CHARPOS editor primary command. The character position information has been turned on.

The user entered either an insert, copy or repeat prefix command in a File Manager/Db2 editor session of an object that contains a binary large object column. Insert, repeat and copy are not supported when the object being processed contains a binary large object column. The operation cannot be performed.

The File Manager View Load Module utility encountered an Binder API error when accessing the module member. The &fc is an internal code to represent the IEWBIND function being executed. The Binder API returned return code &rc and reason code &rsn.