Start of change

HFMBA005   Function name unknown

Explanation

An attempt was made to execute function name. name is not a valid Z Data Tools function.

User response

Check the spelling of the function name and retry with a valid function code.
End of change
Start of change

HFMBA008   Invalid command

Explanation

This generic message is issued when an invalid command is detected.

User response

Check the spelling of the command and check that the command is valid in the current context. Retry with a valid command.
End of change

HFMBA009   Insufficient virtual storage available

Explanation

Z Data Tools does not have enough virtual storage to start or to continue the current function.

User response

Run Z Data Tools with a larger region size.

HFMBA011   Function name is not supported in batch mode

Explanation

You called a Z Data Tools function that cannot be run in batch mode.

User response

Use a different function, or invoke Z Data Tools in a different mode.

HFMBA012   Function name is not included in Z Data Tools for z/OS

Explanation

You called a function that is not part of Z Data Tools for z/OS®.

HFMBA013   Function name is not supported in full-screen mode

Explanation

You called a Z Data Tools function that cannot be run in full-screen mode.

User response

Use a different function, or invoke Z Data Tools in a different mode.

HFMBA014   Function name is not supported in command mode

Explanation

You called a Z Data Tools function that cannot be run in command mode.

User response

Use a different function, or invoke Z Data Tools in a different mode.

HFMBA015   Function name is not supported in line mode

Explanation

You called a Z Data Tools function that cannot be run in line mode.

User response

Use a different function, or invoke Z Data Tools in a different mode.

HFMBA016   Function name is not supported in z/OS

Explanation

You called a Z Data Tools function that is not available.

User response

For a list of functions, refer to Introduction to programming with Z Data Tools functions.

Start of change

HFMBA017   Invalid command: command

Explanation

This generic message is issued when an invalid command is detected. command is the invalid command.

User response

Check the spelling of the command and check that the command is valid in the current context. Retry with a valid command.
End of change
Start of change

HFMBA019   The maximum limit of 255 Find and/or Change search strings has been exceeded

Explanation

The maximum number of Find and Change search strings that can be specified is 255. The operation cannot be performed.

User response

Specify 255 or fewer Find and Change search strings and then retry the operation.
End of change
Start of change

HFMBA029   Deselected segment name (Short).
The segment name entered was recognized, but has been deselected by the current view (Long).

Explanation

A valid segment name was specified, but the current view is not displaying that segment.

User response

Change the view to examine the specified segment.
End of change

HFMBA031   Z Data Tools security setup failed - RACROUTE R15 X'nn', RC X'nn', RSCD X'nn',

Explanation

Z Data Tools is unable to get RACF® information via RACROUTE. For more information, refer to the RACROUTE return and reason codes.

User response

Ensure that your RACF environment is set up correctly. Refer to your RACF documentation, the Z Data Tools Program Directory, and the Z Data Tools Customization Guide.

HFMBA032   Z Data Tools security setup failed - module 'HFMSECUR' not found in LPA

Explanation

The security exit must exist in LPA.

User response

Refer to the Z Data Tools Program Directory and the Z Data Tools Customization Guide.

HFMBA033   Not authorized for function

Explanation

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

User response

If you need to use this function, contact your system support to enable your user ID for this function or function group. Refer to the Z Data Tools Customization Guide.

To determine the resource permission required for the failing function, see "Unprotected functions and profile names for protected functions" in the Z Data Tools Customization Guide.

HFMBA036   Not authorized for fullpack access to VOLSER volser

Explanation

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

User response

If you need to use fullpack disk functions, contact your system support to enable your user ID for fullpack access as described under “Customizing the Security Environment” in the Z Data Tools Customization Guide.

HFMBA037   Function name not supported in authorized mode

Explanation

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

User response

Invoke Z Data Tools in unauthorized mode.

HFMBA038   VOLSER xxxxxx too large for fullpack access

Explanation

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

User response

Use a smaller disk

HFMBA040   Panel display error rc for panel name

Explanation

The panel cannot be displayed.

User response

Save any system error information and contact your system support.

Start of change

HFMBA044   Not all stats available (Short).
Some members were ignored because ISPF statistics were not available (Long).

Explanation

This message is issued by the member selection code. ISPF statistics were not available for all members. This resulted in some members being ignored.

User response

None.
End of change
Start of change

HFMBA051   You cannot set this option with level field blank

Explanation

The Set Offset option was selected, but no value was specified in the Level field. A Level value is required.

User response

Specify a value for Level.
End of change
Start of change

HFMBA052   You cannot set this option with both level and field name blank

Explanation

The Set Offset option was selected, but no value was specified in the Level or Field Name field. A value is required for both fields.

User response

Specify a value for both the Level and Field Name fields.
End of change

HFMBA055   WRITE(&dd) issued that would cause a re-open of a file with UNIT=AFF specified

Explanation

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.

User response

Examine the logic in your procedure and correct the logic so that you are not writing to one file then the next file and then the previous file again.

HFMBA063   VSAM Return code=rc Error code=error code

Explanation

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.

User response

Look up the VSAM return and error codes in DFSMS Macro Instructions for Data Sets for further information.

HFMBA065   Z Data Tools profile save failed

Explanation

Z Data Tools was updating the profile and an error occurred.

User response

Check the HFMPROF allocation or the HFMPROF specification in the installation profile. Refer to the Z Data Tools Customization Guide.

HFMBA066   Z Data Tools profile not found or in error, defaults used

Explanation

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

User response

HFMBA067   Z Data Tools profile parameter parameter=value unknown, defaults used

Explanation

An invalid parameter was found in the Z Data Tools installation profile. The default values supplied by IBM are used.

User response

HFMBA068   Profile error on or near 'parameter', Z Data Tools defaults used

Explanation

A syntax error was detected in the Z Data Tools installation profile, in or near the indicated parameter. The job continues using the HCL-supplied defaults.

User response

Correct the user-supplied Z Data Tools profile. Refer to the Z Data Tools Customization Guide.

HFMBA075   Required HOSTNAME parameter not specified.

Explanation

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

User response

Contact your system support.

HFMBA076   HFI is not at the minimum required service level.

Explanation

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

User response

Upgrade HFI to the required service level and then rerun Z Data Tools.

HFMBA081   No User data associated with this section.

Explanation

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

User response

None.

Programmer response

None.

HFMBA082   No text data associated with this section.

Explanation

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

User response

None.

Programmer response

None.

HFMBA083   RECLIMIT nnnnn start value exceeds nnnnn record length

Explanation

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

User response

Use the SET function and set the RECLIMIT start to a position within the record, then rerun the function.

HFMBA084   REXX not available, printout routed to SYSPRINT

Explanation

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

User response

Use SET PRINTOUT=REXX only when calling Z Data Tools from a REXX procedure.

HFMBA085   No Zap data associated with this section.

Explanation

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

User response

None.

Programmer response

None.

HFMBA091   Missing or invalid control card

Explanation

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

User response

Correct the control card and rerun the job.

HFMBA092   Parameter parameter is missing

Explanation

You omitted a required parameter.

User response

Provide all required parameters.

HFMBA093   Missing or invalid function code

Explanation

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

User response

Provide the correct function code in the control statement.

HFMBA094   Invalid syntax near card column nn

Explanation

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

User response

Correct the control statement.

HFMBA095   Too many parameters

Explanation

You might have specified excessive or duplicate parameters.

User response

Remove excessive or duplicate parameters.

HFMBA096   Parameters parameter1 and parameter2 are mutually exclusive

Explanation

You specified two parameters that cannot be used together.

User response

Provide the correct parameters.

HFMBA097   Parameter parameter1 or parameter2 missing

Explanation

You did not supply a required parameter.

User response

Specify one of the indicated parameters.

HFMBA098   Parameter parameter1 or parameter2 or parameter3 missing

Explanation

You did not supply a required parameter.

User response

Specify one of the indicated parameters.

HFMBA099   Invalid continuation, syntax error near card column nn

Explanation

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

User response

Either remove the continuation indicator or correct the continuation card.

HFMBA100   Unexpected end of parameter specification

Explanation

The parameters for the Z Data Tools invocation are terminated by a comma.

User response

Correct the parameter specification for Z Data Tools invocation.

HFMBA101   IMS function requested and IMS component is not available

Explanation

You have tried to use a ZDT/IMS function, but the ZDT/IMS load module, HFMMOD1, failed to load. This module might have been deleted or protected (for example, if the functions supported by this module are not needed at your installation).

User response

If you need to use this function, contact your system support.

HFMBA102   Db2 function requested and Db2 component is not available

Explanation

You have tried to use a ZDT/Db2 function, but the ZDT/Db2 load module, HFMMOD2, failed to load. This module might have been deleted or protected (for example, if the functions supported by this module are not needed at your installation).

User response

If you need to use this function, contact your system support.

HFMBA113   Parameter parameter invalid or not applicable for this function

Explanation

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

User response

Correct the Z Data Tools invocation or the control statement.

HFMBA114   Parameter parameter is ambiguous

Explanation

Z Data Tools cannot determine an abbreviated parameter that you specified.

User response

Specify the full parameter name.

HFMBA115   Value of parameter parameter missing

Explanation

A value for the specified parameter could not be found.

User response

Correct the Z Data Tools invocation or the control statement.

HFMBA116   Extraneous parameter parameter ignored

Explanation

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

User response

Remove the parameter from the Z Data Tools invocation or the control statement.

HFMBA117   Invalid value for parameter parameter

Explanation

You specified an incorrect value for a parameter.

User response

Correct the Z Data Tools invocation or the control statement.

HFMBA118   Value of parameter parameter too long

Explanation

You specified an incorrect value for a parameter.

User response

Correct the Z Data Tools invocation or the control statement.

HFMBA119   Value out of range for parameter parameter

Explanation

You specified an incorrect value for a parameter.

User response

Correct the Z Data Tools invocation or the control statement.

HFMBA120   Invalid or inconsistent KEYLOC or KEYLEN value

Explanation

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.)

User response

Change the key length, the key location, or both.

HFMBA121   Increment value too high

Explanation

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

User response

Change increment or key length.

HFMBA130   No print feature on SYSPUNCH device

Explanation

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

User response

Copy to cards without interpreting, or allocate SYSPUNCH to a card punch that has a print feature.

HFMBA131   No Compiler options associated with this section

Explanation

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

User response

None.

Programmer response

None.

HFMBA133   ddname DD is allocated to a dummy device

Explanation

There is no data set available for processing. Z Data Tools cannot process dummy data sets.

User response

Allocate a real data set, and rerun the function.

HFMBA134   HFMIIPRT DD must be same unit as SYSPUNCH DD

Explanation

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

User response

Allocate HFMIIPRT with unit affinity to SYSPUNCH.

HFMBA150   End of xxxxx tape sensed

Explanation

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.

User response

If the tape stops before its physical end, you can proceed with caution if required (for example to copy a broken tape to its physical end).

HFMBA151   type="RDF" requires name="field name" attribute to be specified.

Explanation

An XML template contains a <criteria type=”RDF”> element for REDEFINES criteria without the name=”field name” attribute to associate the criteria with a valid REDEFINES field name. The XML template cannot be processed, and the associated function will fail.

Programmer response

Add the attribute name=”field name” where field name is the name of a field with a REDEFINES clause or a field that is the target of a REDEFINES clause.

HFMBA152   name="field name" attribute error. Level 1 field name invalid.

Explanation

An XML template contains a <criteria type=”RDF” name=”field name”> element for redefines criteria. The field name specified is a level 1 field, which is not a valid redefines field.

Programmer response

Change the XML field name to a field that has a REDEFINES clause or a field that is the target of a REDEFINES clause.

HFMBA153   name="field name" attribute error. Field must have or be the target of a REDEFINES clause.

Explanation

An XML template contains a <criteria type=”RDF” name=”field name”> element for redefines criteria but the field name is not a valid redefines field.

Programmer response

Change the XML field name to a field that has a REDEFINES clause or a field that is the target of a REDEFINES clause.

HFMBA156   End of xxxxx tape sensed, function terminated

Explanation

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.

HFMBA157   Field must have or be the target of a REDEFINES clause

Explanation

During a template edit session, the prefix commands CF and CR are only valid for redefines fields.

Programmer response

Issue the prefix command against fields that have a REDEFINES clause or are the target of a REDEFINES clause.

HFMBA158   No redefines criteria for this field in the associated template

Explanation

During an IMS view edit session, the prefix commands CF and CR are used for viewing redefines criteria that have been defined in the associated template. The field referenced by the prefix command does not have any redefines criteria.

Programmer response

Issue the prefix command against field references that are highlighted in red, indicating that redefines criteria exist in the associated template.

HFMBA159   No "by field" expression for this field in the associated template

Explanation

The prefix command CF or option 1 from a redefines criteria expression panel has been selected against a field in an IMS view. The expression in the associated template was entered in free format (CR command as opposed to CF command) so no "by field" display can be shown.

Programmer response

None. This expression cannot be viewed in "by field" format.

HFMBA160   Unit unit does not support Erase Tape

Explanation

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

User response

Mount the tape on an IBM 3400 tape unit (or its equivalent) to perform this function.

HFMBA162   Error on xxxxx tape, ECB ecb, CSW csw, sense 0-6 sense

Explanation

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

User response

Save the message text. Scan the console log for an I⁄O error message, and save it. If the error persists, give the message text to your system support.

HFMBA163   Bypass record - B, ignore error - I, user correct - C

Explanation

An error was found reading from an input tape.

User response

Reply B to skip the record and read the next record. Reply I to use the record as it was read into the input buffer. Reply C to correct the record.

HFMBA170   No EOD delimiter is set

Explanation

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.

User response

Specify a different number of files or use the SET function to define an EOD delimiter.

HFMBA171   Input record exceeds nnnnn byte buffer

Explanation

Z Data Tools could not allocate a buffer large enough for the record.

User response

Rerun the function with more virtual storage.

HFMBA172   nnnnn byte input block exceeds nnnnn byte buffer

Explanation

Z Data Tools could not allocate a buffer large enough for the block.

User response

Rerun the function with more virtual storage.

HFMBA181   No more data found on input tape

Explanation

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

HFMBA191   Invalid element

Explanation

The Z Data Tools XML parser has detected one of the following:
  • Invalid XML where it was expecting to find an element definition.
  • An element definition that isn't valid for the current XML schema.

User response

None.

Programmer response

This message is followed by HFMBA665 or HFMBA666 and HFMBA667, which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA192   Invalid attribute for element <&ELEM>

Explanation

The Z Data Tools XML parser has detected one of the following:
  • Invalid XML where it was expecting to find an attribute definition.
  • An attribute definition that isn't valid for the current XML schema.

User response

None.

Programmer response

This message is followed by HFMBA665 or HFMBA666 and HFMBA667, which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA193   Duplicate attribute &ATTR specified for element &ELEM

Explanation

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

User response

None.

Programmer response

This message is followed by HFMBA665 or HFMBA666 and HFMBA667, which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA194   End tag missing for element &ELEM

Explanation

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

User response

None.

Programmer response

This message is followed by HFMBA665 or HFMBA666 and HFMBA667, which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA195   End tag invalid for element &ELEM

Explanation

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

User response

None.

Programmer response

This message is followed by HFMBA665 or HFMBA666 and HFMBA667, which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA196   Invalid data beyond final end tag

Explanation

Invalid XML - data found beyond final end tag.

User response

None.

Programmer response

This message is followed by HFMBA665 or HFMBA666 and HFMBA667, which display the line number and line text where the error occurred. Either the length of the XML or XML sent is in error. Correct the XML input and retry.

HFMBA197   Severe internal error processing XML

Explanation

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

User response

None.

Programmer response

This message is followed by HFMBA665 or HFMBA666 and HFMBA667, which display the line number and line text where the error occurred. Analyze the preceding messages and action appropriately. You may need to contact HCL Support.

HFMBA198   Data around error: '&DATA'

Explanation

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

User response

None.

Programmer response

This message is followed by HFMBA199 which indicates where the error occurred. Analyze the preceding messages and action appropriately. You may need to contact HCL Support.

HFMBA199   Error occurred: '&DATA'

Explanation

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

User response

None.

Programmer response

This message is preceded by HFMBA198, which displays data around where the error occurred. Analyze the preceding messages and action appropriately. You may need to contact HCL Support.

HFMBA214   Listing option changed to wide to support Text comparison

Explanation

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.

User response

None.

Programmer response

None.

HFMBA215   &nn Control sections processed

Explanation

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

User response

None.

Programmer response

None.

HFMBA216   Only the load module has been processed because the summary option is selected.

Explanation

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.

User response

None.

Programmer response

None.

HFMBA218   No disk record found

Explanation

The specified disk record does not exist on this track.

User response

If appropriate, specify a lower disk record number.

HFMBA219   No home address record

Explanation

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

User response

Rerun the function. If the problem recurs, contact your system support.

HFMBA220   Should new EOF be written after this record? Y or N

Explanation

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).

User response

If you want a new end-of-file record to follow this record, reply Y. Otherwise, enter N or U to exit the function.

HFMBA230   Invalid element <&ELEM.> value: &VAL

Explanation

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

User response

None.

Programmer response

This message is followed by HFMBA665 or HFMBA666 and HFMBA667, which display the line number and line text where the error occurred. It may be preceded by messages giving more detail as to the specific problem. Correct the XML input and retry.

HFMBA231   Invalid CDATA ']]>' missing <&ELEM.>

Explanation

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

User response

None.

Programmer response

This message is followed by HFMBA665 or HFMBA666 and HFMBA667, which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA232   Child element <&ELEM.> with wrong parent

Explanation

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

User response

None.

Programmer response

This message is followed by HFMBA665 or HFMBA666 and HFMBA667, which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA233   <&ELEM.> not specified

Explanation

A required element has not been specified.

User response

None.

Programmer response

This message is followed by HFMBA665 or HFMBA666 and HFMBA667, which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA234   Library number &no exceeds number of <library> elements

Explanation

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

User response

None.

Programmer response

This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA235   Attribute &ATTR invalid value &VAL

Explanation

The attribute value specified is invalid for the current element.

User response

None.

Programmer response

This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA236   Template could not be updated - criteria would be lost

Explanation

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.

User response

None.

Programmer response

Change the template to remove the field references that have been deleted in the latest version of the copybooks or change the copybooks to include the required field references and retry the update. Alternatively you can specify the REPLACE=YES option to override the existing template.

HFMBA237   id attribute not specified or invalid symbol number - &ID

Explanation

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

User response

None.

Programmer response

This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA238   related01="&ID." attribute specified invalid symbol number

Explanation

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.

User response

None.

Programmer response

This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA239   type attribute not specified or invalid - &TYPE

Explanation

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.

User response

None.

Programmer response

This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA240   byfield="1" required for dynamic template

Explanation

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

User response

None.

Programmer response

This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA241   Only type="SEL" allowed for dynamic template.

Explanation

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

User response

None.

Programmer response

This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA242   Expression exceeds allowable length.

Explanation

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

User response

None.

Programmer response

Reduce the expression length. This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA243   Expression error around offset &nn.

Explanation

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

User response

None.

Programmer response

Check any preceding error message and correct the expression. This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA244   Symbol ref=&REF is invalid for current layout - Should be in range &LOW to &HIGH.

Explanation

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.

User response

None.

Programmer response

Correct the reference number. This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA245   Symbol ref=&ref out of order

Explanation

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

User response

None.

Programmer response

Correct the reference number. This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA246   Symbol ref=&ref start valure required

Explanation

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

User response

None.

Programmer response

Specify the start value. This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA247   Symbol ref=&ref start value cannot be zero

Explanation

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

User response

None.

Programmer response

Provide a positive integer value for start or specify offset="1" on the <symbol > tag. This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA248   Symbol ref=&ref Invalid type attribute.

Explanation

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

User response

None.

Programmer response

Specify a valid type attribute. This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA249   Symbol ref=&ref Invalid length attribute.

Explanation

When you are creating a dynamic template the length attribute must be one of these values:
PD
Must be between 1 and 16.
BI
Must be 1, 2, 4 or 8.
ZD
Must be between 1 and 32.
FP
Must be 4 or 8.
FE
Must be >6 and <24. The precision is the length minus 6. The scale is the precision minus 1.
DBCS strings
Must be an even number of bytes.

User response

None.

Programmer response

Specify a valid length attribute. This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA252   Output tape not positioned at load point or after EOF labels

Explanation

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

User response

Ensure that the tape is positioned correctly and rerun the function, or rerun the function without label processing.

HFMBA253   No xxxxxx label found on input tape

Explanation

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

User response

Mount a labeled tape. Position it at the data set you want to process and rerun the function, or rerun the function without label processing.

HFMBA254   No xxxxxx label found on output tape

Explanation

The output continuation volume is not a standard label tape.

User response

Ensure that all output volumes are initialized with standard labels and rerun the function, or rerun the function without label processing.

HFMBA260   Symbol ref=&ref heading too long.

Explanation

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

User response

None.

Programmer response

Specify a shorter heading. This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA261   Symbol ref=&ref <createn> element invalid for non numeric symbol.

Explanation

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

User response

None.

Programmer response

Remove the <createn> element. This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA262   element value too long

Explanation

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

User response

None.

Programmer response

Correct the length of the element data. This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA263   Element in conflict with previously specified elements or type

Explanation

The element specified in the following HFMBA230 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.

User response

None.

Programmer response

This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA264   Required attributes not specified.

Explanation

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.

User response

None.

Programmer response

This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA265   Scramble translate attribute requires translate element.

Explanation

<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.

User response

None.

Programmer response

This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA267   <criteria> must specify byfield="1" for <byline> to be valid

Explanation

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

User response

None.

Programmer response

This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA268   <describe> exceeds maximum 5 elements.

Explanation

Too many <describe> elements have been specified.

User response

None.

Programmer response

This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA269   template required - command cannot be processed.

Explanation

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

User response

None.

Programmer response

This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA271   <copybooks> can only be specified for a copybook template

Explanation

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

User response

None.

Programmer response

Remove the <copybooks> element and children. This message is followed by HFMBA230 to identify the element, and by messages HFMBA665, or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA273   related01="&ID." attribute specified without type="RID" attribute

Explanation

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

User response

None.

Programmer response

Correct the XML to specify type="RID" attribute. This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA278   Element has exceeded maximum occurrences

Explanation

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

User response

None.

Programmer response

This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA279   Required element or child element not specified.

Explanation

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.

User response

None.

Programmer response

This message is followed by HFMBA230 to identify the element, and by messages HFMBA665 or HFMBA666 and HFMBA667 which display the line number and line text where the error occurred. Correct the XML input and retry.

HFMBA281   Error on xxxxx tape, not a valid Exported Stacked Volume

Explanation

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.

User response

Correct the input and retry the request.

HFMBA282   Error on xxxxx tape, bad table of contents on input volume

Explanation

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

User response

Correct the input and retry the request.

HFMBA283   Error logical volume xxxxx not found in TOC of volume vvvvvv

Explanation

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.

User response

Correct the input and retry the request.

HFMBA284   Error duplicate logical volume vvvvvv in request list

Explanation

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

User response

Correct the input and retry the request.

HFMBA298   Output volume xxxxxx not long enough for logical volume vvvvvv

Explanation

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.

User response

Mount an output volume of suitable length.

HFMBA299   Error code nn processing Exported Stacked Volume

Explanation

An unexpected error occurred while processing the input Exported Stacked Volume. The error code nn gives an indication of the problem:
01–03
Initial input volume positioning error. Possible drive error.
06–10
Error processing header labels on input volume. Possible bad input volume.
15–24
Error during Exported Stacked Volume verification process. This is not a volume created by the VTS export function, or the volume has become corrupted.
30–34
Error reading the Table of Contents file from the Exported Stacked Volume. The Table of Contents file on the Exported Stacked Volume may be corrupted.
40–48
Logical volume could not be correctly located on the Exported Stacked Volume. The volume may be corrupted.
49
Logical volume could not be correctly located on the Exported Stacked Volume. The drive on which the input Exported Stacked Volume is mounted may not support the locate block CCW, or the volume may be corrupted.
50–51
Error during copy process. Possible drive error.
55–58
Error during listing process. Possible drive error.
60–62
Error positioning output volume. Possible drive error.
66–79
Internal VTS record format error. The volume may be corrupted.
85–86
Error writing to output volume. Possible drive error.
90–93
Unable to obtain storage for work areas. Error codes 90–92 indicate that the storage has been requested above the 16M line. Error code 93 indicates that the storage has been requested below the 16M line.
95
General copy error. See earlier message for more detailed error code.

User response

Take corrective action according to the error code.

HFMBA301   unit is invalid device for this function

Explanation

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.)

User response

Use a valid device for this function, or use a Z Data Tools function appropriate for the device specified.

HFMBA310   Data set dsname not found

Explanation

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

User response

Correct the data set name in the DD statement, in the Z Data Tools invocation, or in the control statement.

HFMBA311   No ddname DD statement supplied

Explanation

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

User response

Correct the JCL or the INPUT or OUTPUT parameter, and rerun the job. To access a tape again after a TLT function, end the job step and continue with another step.

HFMBA314   WARNING: dsname in use. function continues without exclusive control

Explanation

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

User response

Ensure that your update request does not expose the data or the other task and continue, or run the function when the data set is available for exclusive control.

HFMBA315   Data set request denied by SVC99 validation routine

Explanation

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

User response

Contact your system support.

HFMBA316   ddname DD open failed, ABEND code abend-reason

Explanation

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

User response

Refer to the accompanying system message, and check the status of the data set or tape.

HFMBA317   Invalid xxxxxx data set for function xxx

Explanation

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.

User response

Specify a function capable of processing the data. You can use basic disk functions to inspect data with unknown organization.

HFMBA318   type data set ddname macro failed, ABEND code xxxx-xxx

Explanation

The indicated operation failed for the indicated data set.

User response

Check for any accompanying system messages, and refer to the appropriate system manual.

HFMBA319   type data set ddname macro RC xxxx-xxxx

Explanation

The indicated operation failed for the indicated data set.

User response

Check for any accompanying system messages, and refer to the appropriate system manual.

HFMBA320   No SYSPRINT DD statement supplied

Explanation

Z Data Tools requires SYSPRINT to be allocated.

User response

Ensure that a SYSPRINT DD statement is supplied, then rerun the job.

HFMBA321   EOV for xxxx failed, ABEND code xxxx-xxxx

Explanation

An ABEND occurred during EOV processing for the indicated tape.

User response

Check for any accompanying system messages, and refer to the appropriate system manual. If the problem persists, contact your system support.

HFMBA322   SL and NON SL functions cannot be used in the same execution

Explanation

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.

User response

Allocate the tape for non-standard label processing and retry the function.

HFMBA323   SL and NEW requested for NON SL function

Explanation

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

User response

Allocate the tape for non-standard label processing and retry the function.

HFMBA331   Permanent I/O error on input|output ECB hhhhhhhh

Explanation

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

User response

Refer to the corresponding system message for more information.

HFMBA332   Permanent data check on input|output, CSW csw, sense code

Explanation

This is probably a hardware error.

User response

Refer to the hardware device reference manual for an interpretation of the CSW and the sense bytes.

HFMBA333   Read error, incorrect block length on input/output

Explanation

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

User response

Change the DCB parameter of the DD and rerun the job, or try using a tape or disk function instead of a QSAM function to process this data set.

HFMBA350   Block size (xxxx) invalid for FIXED, recsize output

Explanation

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

User response

Specify a different block size or a different record size.

HFMBA351   Input data length (length) not multiple of recsize (recsize)

Explanation

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

User response

Correct the input specification or use the SET PAD processing option to adjust the input records.

HFMBA352   Block size (nnnnn) exceeds maximum (max)

Explanation

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

User response

Specify a smaller block size.

HFMBA353   Record size (recsize) exceeds maximum (max)

Explanation

A record exceeds the maximum record size allowed for the output data set. This message might be issued if an output data set has inconsistent RECSIZE and BLKSIZE parameters. For example:
  • RECFMOUT=VB and BLKSIZE is less than RECSIZE + 8
  • RECFMOUT=V, B, or DB, and BLKSIZE is less than RECSIZE + 4

User response

Specify a smaller record size, or change the output data set definition.

HFMBA354   Block size (blksize) not multiple of record size (recsize)

Explanation

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.

User response

Specify a different block size or a different record size.

HFMBA355   Record size (nnnnn) invalid for FIXED,nnnnn output

Explanation

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

User response

Correct the input or output specification or use the SET PAD processing option to adjust the input records.

HFMBA356   Inconsistent record size (nnnnn) for FIXED,nnnnn input

Explanation

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

User response

Correct the input or output specification.

HFMBA358   Inconsistent record length field X'nnnnn'

Explanation

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

User response

Correct the input data, limit processing to stop before the incorrect block, or correct the input specifications.

HFMBA359   REXX variable var is empty

Explanation

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

User response

Initialize the REXX variable in your procedure with the desired value before invoking Z Data Tools.

HFMBA360   REXX Stem count var invalid

Explanation

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

User response

Initialize the REXX variable in your procedure with the correct stem count before invoking Z Data Tools.

HFMBA361   Incorrect block length field X'xxxx', block nnnn, length nnnn

Explanation

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.

User response

Correct the input data, limit processing to stop before the incorrect block, or correct the input specifications.

HFMBA362   Incorrect record length field X'xxxx', block nnnn, offset nnnn

Explanation

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

User response

Correct the input data, limit processing to stop before the incorrect block, or correct the input specifications.

HFMBA363   Incorrect spanned record segmentation, block nnnn, record nnnn

Explanation

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

User response

Correct the input data, limit processing to stop before the incorrect block, or correct the input specifications.

HFMBA370   Key positioning not possible

Explanation

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

User response

Remove the key position specification.

HFMBA371   Output data set not ESDS

Explanation

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.

User response

Specify an ESDS as the output data set.

HFMBA372   Inconsistent key length or key position

Explanation

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.

User response

Check that you really intended to change the key position or key length.

HFMBA375   VSAM macro RC rc, Error Code X'xx' yyy

Explanation

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.

X'xx' is, in hexadecimal:
  • The error byte of the ACB if OPEN or CLOSE failed
  • The error byte of the RPL if POINT, GET, or PUT failed
  • The contents of Register 0 if SHOWCB or TESTCB failed

yyy might present additional information about the error.

User response

Take corrective action as described in the documentation for your current release of VSAM.

HFMBA378   VSAM catalog RC nn, RSCD IGG0CLxx - nnn...

Explanation

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.

User response

Take the appropriate action based on the explanation of the codes.

HFMBA393   OPEN warning code X'xx' yyy. Continue ? Y or N

Explanation

VSAM OPEN returned a warning code indicated in the message. Z Data Tools 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.

User response

Take corrective action as described in the documentation for your current release of VSAM. Enter Y to continue, or N to exit from the function.

HFMBA394   OPEN warning code X'nn'(condition). Processing continues.

Explanation

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

Condition is a terse form of the explanation for some reason codes, as given by DFSMS Macro Instructions for Data Sets as follows:
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

User response

Consider the terse description and consult the DFSMS Macro Instructions for Data Sets manual for the OPEN reason code listed to determine if this condition is expected.

HFMBA395   Recovery from invalid RBA (nnnnn) failed

Explanation

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

User response

Enter an RBA matching the beginning of a record.

HFMBA396   SHOWCAT for input|output data set failed, RC rc

Explanation

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.

User response

Take the appropriate action based on the explanation of the codes.

HFMBA397   DIV req request error, RC nn, Reason Code rsn

Explanation

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.

User response

Take the appropriate action based on the explanation of the codes.

HFMBA401   Input|Output tape on unit is vol1, not volser.

Explanation

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

User response

Ensure that you are using the correct volumes, check for incorrectly specified volume serial numbers, and rerun the function.

HFMBA407   Tape volume to be labeled on unit. Enter 'volser', Cancel - U

Explanation

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

User response

Enter a serial identification to be used for the volume, or enter U to cancel.

HFMBA409   Unexpired file name date on tape unit,vol1. Ignore - I, Cancel - U

Explanation

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

User response

Ensure that the tape can be used for output and enter I to continue, or enter U to cancel.

HFMBA411   Ready unit, then press ENTER

Explanation

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

User response

Ensure that the correct device is attached and assigned. Ready the device and press Enter. Enter QUIT, CANCEL, EXIT, or EOJ to terminate.

HFMBA413   Manual unload/rewind detected on unit, press ENTER to rewind and continue

Explanation

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

User response

Press Enter to rewind and continue, or enter QUIT, CANCEL, EXIT, or EOJ to terminate.

HFMBA420   Line &NO Syntax error detected at column &COL in the following statement.

Explanation

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.

User response

None.

Programmer response

Check the preceding messages and correct the procedure. If this message is produced and a template expression is being run then an internal error has occurred and you need to contact HCL Support.

HFMBA421   Keyword being processed: &KWD

Explanation

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

User response

None.

Programmer response

Check the preceding messages and correct the procedure.

HFMBA422   &statement

Explanation

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.

User response

None.

Programmer response

Check the preceding messages and correct the procedure.

HFMBA423   Error - one of the following keyword expected.

Explanation

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

User response

None.

Programmer response

Check the following messages and correct the procedure.

HFMBA424   The function is incomplete - no closing parenthesis found

Explanation

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

User response

None.

Programmer response

Provide the missing parenthesis and rerun.

HFMBA425   The condition is incomplete

Explanation

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

User response

None.

Programmer response

Correct the condition and rerun.

HFMBA426   Incomplete DO levels in procedure - END statements required

Explanation

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

User response

None.

Programmer response

Provide the missing end statements and rerun.

HFMBA427   Incomplete quoted string - closing quote/apostrophe required

Explanation

A literal value has been coded that begins with a quotation mark or apostrophe and no ending quotation mark or apostrophe has been coded.

User response

None.

Programmer response

Provide the closing quotation mark or apostrophe and rerun.

HFMBA428   Incomplete comment - closing */ required

Explanation

A REXX comment is incomplete.

User response

None.

Programmer response

Provide the closing */ and rerun.

HFMBA429   Invalid continuation comma on last statement in procedure

Explanation

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

User response

None.

Programmer response

Correct by either removing the comma or providing the continued statement and rerun.

HFMBA430   Right parenthesis missing

Explanation

A conditional statement has unbalanced left and right parenthesis.

User response

None.

Programmer response

Provide the same number of right and left parenthesis in the conditional statement referenced and rerun.

HFMBA431   Invalid operator found in condition

Explanation

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

User response

None.

Programmer response

Correct the operator to be valid REXX operator and rerun.

HFMBA432   Keyword not supported for FASTREXX processing

Explanation

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

User response

None.

Programmer response

Either change the keyword to an equivalent FASTREXX supported keyword or remove the *FASTREXX ON card to allow REXX to process.

HFMBA433   Internal error - Format template ptr for &nn.th record type is zero.

Explanation

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

User response

None.

Programmer response

Contact HCL Support.

HFMBA434   Internal error - FASTREXX Function &FUN not found in Z Data Tools REXX function load module HFMRXFUN

Explanation

HFMRXFUN load module is not the same level or version as the HFMMAIN load module.

User response

None.

Programmer response

Installation problem. Check where these load modules are being run from and ensure your job is loading the correct modules. Contact your systems programmer and check your installation.

HFMBA435   Internal error - Z Data Tools load modules HFMMAIN and HFMRXFUN are not at the same version/level

Explanation

HFMRXFUN load module is not the same level or version as the HFMMAIN load module.

User response

None.

Programmer response

Installation problem. Check where these load modules are being run from and ensure your job is loading the correct modules. Contact your systems programmer and check your installation.

HFMBA436   Function &FUN function call failed rc = &RC.

Explanation

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

User response

None.

Programmer response

Check the preceding messages which should indicate the problem with the function parameters - correct and rerun.

HFMBA437   SIGNAL statement has no label

Explanation

A SIGNAL statement has been coded without a label value.

User response

None.

Programmer response

Provide the correct label value for the statement and rerun.

HFMBA438   Internal function coded incorrectly.

Explanation

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

User response

None.

Programmer response

Contact HCL Support.

HFMBA440   Line &nn Expression always true at column &col in the following statement

Explanation

Informational message to say the indicated condition is always true.

User response

None.

Programmer response

Correct the logic if required.

HFMBA441   Line &nn Expression always false at column &col in the following statement

Explanation

Informational message to say the indicated condition is always false.

User response

None.

Programmer response

Correct the logic if required.

HFMBA442   logical value not 0 or 1

Explanation

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

User response

None.

Programmer response

Correct the condition and rerun.

HFMBA443   Field reference

Explanation

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

User response

None.

Programmer response

Examine all related messages and correct the procedure accordingly.

HFMBA444   SIGNAL &label statement unresolvable

Explanation

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

User response

None.

Programmer response

Either provide the label or correct the SIGNAL statement to refer to a valid label name and rerun.

HFMBA445   No executable logic in procedure

Explanation

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

User response

None.

Programmer response

A procedure must have at least one statement that can be run to be a valid procedure.

HFMBA446   SIGNAL &lab causes infinite loop

Explanation

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

User response

None.

Programmer response

Correct the logic flow and rerun.

HFMBA448   Constant - numeric or character

Explanation

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

User response

None.

Programmer response

Examine all related messages and correct the procedure accordingly.

HFMBA449   Z Data Tools external function

Explanation

This message may be produced when listing the expected keywords for message HFMBA423. It indicates that a Z Data Tools external function is an allowed keyword.

User response

None.

Programmer response

Examine all related messages and correct the procedure accordingly.

HFMBA450   External CICS interface program DFHXCIS cannot be loaded

Explanation

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 Z Data Tools function.

User response

None.

Programmer response

Check the Z Data Tools setup. Make sure the cicshlq.SDFHEXCI load library is defined in the following ways depending on how you are using Z Data Tools:
  • to the STEPLIB or the LINKLIST (for a TSO or batch session)
  • to the HFMLIB or LINKLIST for the ZCC server (when using ZDT/CICS)
See "Setting up CICS access for Z Data Tools base component" in the Z Data Tools Customization Guide.

HFMBA451   External CICS interface &FUNC failed Resp=&RESP, Reason=&REAS

Explanation

Z Data Tools 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

User response

None.

Programmer response

Ensure that the steps documented in " Setting up CICS access for Z Data Tools base component" in the Z Data Tools Customization Guide have been performed. If they have been completed successfully then refer to the manual CICS Transaction Server for z/OS CICS External Interface Guide and search for the function documented in the message. The response and reason codes are documented. Check them and action accordingly or contact HCL Support.

HFMBA453   External CICS interface - DPL CICS LINK failed RESP=&RESP, RESP2=&RESP2, Abend=&ABCODE

Explanation

Z Data Tools has attempted to access a CICS region using the external CICS interface and has failed to perform the a DPL CICS Link to the HFM3CICS program with the responses documented in the message. This would normally be a setup problem.

User response

None.

Programmer response

Ensure that the steps documented in " Setting up CICS access for Z Data Tools base component" in the Z Data Tools Customization Guide have been performed. If they have been completed successfully then refer to the CICS Transaction Server for z/OS CICS External Interface Guide and search for the function documented in the message. The response and reason codes are documented. Check them and action accordingly or contact HCL Support.

HFMBA454   Failed to start server CICS applid &CICS failed RC=&RC RESP=&RESP, RESP2=&RESP2

Explanation

Z Data Tools has attempted been unable to start a server task in the CICS region requested.

User response

None.

Programmer response

This message precedes HFMBA462 messages which can be used to determine why the server task failed. Contact HCL Support for more assistance.

HFMBA455   Socket create failed Rc=&RC,Reason=&RSN

Explanation

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

User response

None.

Programmer response

Refer to UNIX System Services Messages and Codes for the reason code in the message. If you cannot determine the problem from the manual then contact HCL Support.

HFMBA456   Socket connect failed Rc=&RC,Reason=&RSN

Explanation

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

User response

None.

Programmer response

Refer to UNIX System Services Messages and Codes for the reason code in the message. If you cannot determine the problem from the manual then contact HCL Support.

HFMBA457   Send to CICS applid &CICS failed Rc=&RC,Reason=&RSN

Explanation

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

User response

None.

Programmer response

Refer to UNIX System Services Messages and Codes for the reason code in the message. If you cannot determine the problem from the manual then contact HCL Support.

HFMBA458   Receive from CICS applid &CICS failed Rc=&RC,Reason=&RSN

Explanation

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

User response

None.

Programmer response

Refer to UNIX System Services Messages and Codes for the reason code in the message. If you cannot determine the problem from the manual then contact HCL Support.

HFMBA459    Send failed for logoff command CICS applid &CICS failed Rc=&RC,Reason=&RSN

Explanation

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

User response

None.

Programmer response

Refer to UNIX System Services Messages and Codes for the reason code in the message. If you cannot determine the problem from the manual then contact HCL Support.

HFMBA460    Socket close failed for CICS applid &CICS failed Rc=&RC,Reason=&RSN

Explanation

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

User response

None.

Programmer response

Refer to UNIX System Services Messages and Codes for the reason code in the message. If you cannot determine the problem from the manual then contact HCL Support.

HFMBA461    CICS server task failed to obtain port for CICS applid &CICS

Explanation

Z Data Tools has tried to initiate the HFM 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.

User response

None.

Programmer response

Check the status of the CICS region to ensure a task can be started and ensure the CICS region has been set up for TCPIP communications. If the problem persists contact HCL Support.

HFMBA462   &CICS_MESSAGE

Explanation

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

User response

None.

Programmer response

Address the error described by the message text or contact HCL Support.

HFMBA463    Socket getaddrinfo failed Rc=&RC,Reason=&RSN

Explanation

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.

User response

None.

Programmer response

Refer to UNIX System Services Messages and Codes for the reason code in the message. If you cannot determine the problem from the manual, then contact HCL Support.

HFMBA464    No HFMCICS DD to produce CICS Applid list

Explanation

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 HFMCICS DD and the HFMCICS DD has not been allocated to the session.

User response

None.

Programmer response

Perform the step to set up the HFMCICS DD as documented in "Setting up CICS access for Z Data Tools base component" in the Z Data Tools Customization Guide.

HFMBA465    Invalid attributes for HFMCICS file must be fixed 80

Explanation

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

User response

None.

Programmer response

Perform the step to set up the HFMCICS DD as documented in the "Setting up CICS access for Z Data Tools base component" in the Z Data Tools Customization Guide.

HFMBA466    Member name required in HFMCICS DD

Explanation

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

User response

None.

Programmer response

Specify the member name on the DD statement and rerun the function.

HFMBA467    The HFMCICS DD has no records - no applid list can be produced

Explanation

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

User response

None.

Programmer response

Edit the data set or member and provide a list of CICS applids and descriptions as specified in "Setting up CICS access for Z Data Tools base component" in the Z Data Tools Customization Guide.

HFMBA470    Authentication DD HFMAUTH not found and required for remote system access.

Explanation

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

User response

None.

Programmer response

Provide a //HFMAUTH DD card for batch JCL or allocate the HFMAUTH DD if running under TSO to the appropriate authentication file.

HFMBA471    Invalid attributes for HFMAUTH - required RECFM VB with LRECL >= &recl

Explanation

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

User response

None.

Programmer response

Delete and allocate the authentication file with record format VB, and a LRECL greater than or equal to the value specified in the message. The data set organization can be physical sequential or partitioned. If a partitioned data set is specified then the allocation or JCL DD card must specify a member name.

HFMBA472   Member name required in HFMAUTH DD.

Explanation

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

User response

None.

Programmer response

Provide a JCL DD or allocation for the DD FMAUTH that includes the appropriate member name.

HFMBA473   HFMAUTH dataset - record &recno length &RECL too long

Explanation

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

User response

None.

Programmer response

If the file has not been changed outside of Z Data Tools then report the problem to HCL Support. Z Data Tools will present you with a list of valid credentials if other records are valid. By making a change to the credentials presented Z Data Tools should correct the authentication data set.

HFMBA474   HFMAUTH dataset - record &RECNO contains corrupted data.

Explanation

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

User response

None.

Programmer response

If the file has not been changed outside of Z Data Tools then report the problem to HCL Support. Z Data Tools will present you with a list of valid credentials if other records are valid. By making a change to the credentials presented Z Data Tools should correct the authentication data set.

HFMBA479   No selection was made for a remote system.

Explanation

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

User response

None.

Programmer response

Select an remote system or remove the remote identifier in the resource name.

HFMBA480   Messages from remote system

Explanation

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

User response

None.

Programmer response

View the proceeding messages and take the appropriate action.

HFMBA481   Messages from remote system

Explanation

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

User response

None.

Programmer response

View the proceeding messages and take the appropriate action.

HFMBA482   Cannot connect to remote systems for this session.

Explanation

This indicates that another task in the address space has a signal handler and Z Data Tools 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.

User response

None.

Programmer response

Normally this applies to ISPF where another session has a language environment that has been initialized with POSIX(ON). You may have to exit that session and depending on whether the address space still appears to be in a dubbed state you may need to logoff and logon again.

HFMBA483   No socket

Explanation

You are running a Z Data Tools function that references a remote resource. An error occurred when creating a socket to connect to a remote Z Data Tools, 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.

User response

None.

Programmer response

This is primarily a TCPIP socket environmental error. Check that TCPIP is configured and operating normally in your environment. Check that the region size is large enough to support some buffer allocations for sockets.

HFMBA484   Peer unresolvable

Explanation

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

User response

Check the peer name is as intended.

Programmer response

Once confirmed that the peer name is correct, consult your TCPIP administrator to determine why the z/OS resolver could not translate the name to an IP. One possibility is that name resolution from the z/OS system being used may require a network suffix to be added to the name.

HFMBA485   Peer connect fail.

Explanation

When attempting to connect to a remote Z Data Tools, the intended peer would not connect.

User response

Check the peer name and port number correctly reflect a running common server on the remote system.

Programmer response

This error occurs when the name of the peer has been resolved, but the connect to the common server at the specified port did not succeed. Presuming that the TCPIP stack is working ok on your current system, then the most likely cause is that the common server is not running on the remote system, or there is a firewall blocking the port connection.

HFMBA486   Check server

Explanation

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.

User response

None.

Programmer response

Confirm that the port is the port of the remote common server. Also confirm that the remote common server is running. Lastly, check that no firewall is creating unexpected traffic on the intended port (e.g an unexpected firewall redirect or authorisation)

HFMBA487   TLS Handshake failed

Explanation

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

User response

None.

Programmer response

Programmer Response: Most likely cause is that a setup step has been missed. The certificate of the remote system must be known to the local system for the handshake to complete. Consult the Z Data Tools Customization Guide for the required steps to achieve this.

HFMBA488   No signon message

Explanation

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

User response

None.

Programmer response

Investigate the remote system server.

HFMBA489   Server does not have HFM

Explanation

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

User response

None.

Programmer response

Check that the server name and port is correct. Otherwise complete the configuration of the server on the remote server to include a Z Data Tools configuration.

HFMBA490   Invalid password

Explanation

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

User response

Correct the password.

Programmer response

None.

HFMBA491   Invalid parameter

Explanation

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

User response

None.

Programmer response

Investigate the remote server configuration. Tracing may need to be activated on the remote server in order to identify and resolve the problem.

HFMBA492   Server environment error

Explanation

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.

User response

None.

Programmer response

Investigate the remote server configuration. Tracing may need to be activated on the remote server in order to identify and resolve the problem.

HFMBA493   Expired password

Explanation

The password for the specified userid on the remote server is expired.

User response

Reset or renew the password for the remote system.

Programmer response

None.

HFMBA494   New password no good

Explanation

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

User response

Reset or renew the password for the remote system.

Programmer response

None.

HFMBA495   Server setup error

Explanation

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

User response

Report to remote server administrator.

Programmer response

Check the SYSLOG of the target server, most likely cause is that the userid of the server is not permitted to the BPX.SERVER resource.

HFMBA496   Unknown userid

Explanation

The userid specified is not known by the target system.

User response

Check the userid and remote server details and enter the correct details.

Programmer response

None.

HFMBA497   Unusable userid

Explanation

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

User response

Check the userid access on the remote system. Most likely a request to have the userid resumed will be needed.

Programmer response

None.

HFMBA498   Unusable userid

Explanation

The userid was refused.

User response

Check the userid access on the remote system. Most likely a request to have the userid resumed will be needed.

Programmer response

If the userid can logon through other means, this indicates a setup problem with the remote server. Server tracing may need to be activated to help identify the problem.

HFMBA499   Common client error

Explanation

An error occurred invoking client.

User response

If the available virtual storage in the region was low, release or increase the region size and retry.

Programmer response

If the problem persists, check the load libraries for HFMCL.

HFMBA516   SSSARSN reason code &RC returned from IEFSSREQ Service request

Explanation

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

User response

Contact your systems programmer.

HFMBA517   Cannot connect to Db2, CAF request RC xx, Reason Code xx

Explanation

Z Data Tools failed to connect to Db2®. The indicated Call Attach Facility request did not complete successfully.

User response

Contact your Db2 administrator.

HFMBA518   Unexpected RC xx returned from IEFSSREQ request, token nnnnnn

Explanation

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

User response

Contact your system support.

HFMBA519   Function terminated by OAM environment error

Explanation

Z Data Tools failed to establish connection with OAM.

User response

Contact system support.

HFMBA520   OAM req failed, RC rc, Reason Code rsn

Explanation

The requested OAM function failed.

User response

For an explanation of the return code and reason code, refer to the documentation for your current release of z/OS.

HFMBA521   Directory request failed, Db2 not accessible

Explanation

The requested OAM function failed. Z Data Tools could not access Db2.

User response

Contact your Db2 administrator.

HFMBA522   Directory request failed, Db2 privilege not granted

Explanation

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

User response

Contact your Db2 administrator. For a list of tables, refer to the Z Data Tools Customization Guide.

HFMBA523   Directory request failed, unexpected SQL RC rc

Explanation

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

User response

Contact your Db2 administrator.

HFMBA524   OAM STORE failed, collection not found or definition denied

Explanation

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

User response

Check your installation SMS specifications for correct class values if necessary.

HFMBA525   Directory request failed with RC rc, trying again...

Explanation

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

HFMBA526   Directory request failed with SQL RC rc, Db2 resource locked

Explanation

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

User response

Rerun the function. If the problem persists, contact your Db2 administrator.

HFMBA529   Skip count exceeds bytes byte object size

Explanation

You asked to skip more bytes than the object contains. You have effectively asked Z Data Tools not to print any data.

User response

Specify a lower skip count value.

HFMBA530   No object header found on input, specify collection and object name

Explanation

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

User response

Specify the collection and object name and rerun the function. To create input data with header records, use functions OS or OV with the HEADER option.

HFMBA534   STOR/MGMT class value overridden by defaults

Explanation

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.

User response

Check your installation SMS specifications for correct class values if necessary.

HFMBA538   Input data not in object dump format

Explanation

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

User response

Correct the input data and rerun the function.

HFMBA539   nnn object(s) could not be dumped

Explanation

Backup of one or more objects failed. Z Data Tools issues this message at the end of the function. Message HFMBA200 shows the OAM error information for each failing object.

User response

Check the Z Data Tools output for message HFMBA200 and take appropriate actions.

HFMBA590   Format of DB field incorrect at offset nnnnn

Explanation

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

Z Data Tools 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.

HFMBA591   Mixed field ends before end of DB subfield at offset nnnnn

Explanation

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.

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

User response

Correct the field definition in the FMT command. Rerun the function.

HFMBA592   One or more records with incorrect DB fields found

Explanation

Z Data Tools has detected incorrect double-byte character set fields in one or more records.

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

User response

Check the listing for message HFMBA590 or HFMBA591 to find the incorrect record.

HFMBA600   Minimum requirement to run this level of Z Data Tools is z/OS

Explanation

To run Z Data Tools V1R1, you need z/OS.

User response

You cannot run Z Data Tools on your system.

HFMBA601   Minimum requirement to run Z Data Tools is DFP 3.3

Explanation

To run Z Data Tools, you need MVS/DFP Version 3 Release 3 or later.

User response

You cannot run Z Data Tools on your system.

HFMBA604   Load of module 'name' failed, module not found

Explanation

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

User response

If you need to use this function, contact your system support.

HFMBA605   Successfully recovered from ABEND

Explanation

An ABEND occurred while Z Data Tools was running. Depending on the circumstances, a dump might be produced.

User response

Check for any system error or Z Data Tools message and take corrective actions. If the problem persists, contact your system support.

HFMBA606   FILE MANAGER ENCOUNTERED AN INTERNAL ERROR - CODE NNNN

Explanation

Z Data Tools encountered an internal problem. The error is identified by the Z Data Tools error code.

User response

Contact your system support.

HFMBA607   FILE MANAGER ABENDED WITH CODE CODE - REASON REASON

Explanation

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

User response

Refer to the documentation for your current release of the z/OS system.

HFMBA608   Load of module xxxxxxxx failed, ABEND code nnnn-nnn

Explanation

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

User response

Refer to the accompanying system message or the system code, and take appropriate action.

HFMBA609   Access to REXX variable pool failed, xxx R15 nn

Explanation

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

User response

Contact your system support.

HFMBA610   Unexpected code returned from REXX variable interface, RC nn

Explanation

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

User response

Contact your system support.

HFMBA613   I/O error on unit, ECB ecb, CSW csw, sense 0-3 sense

Explanation

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

User response

Ensure that you are using the correct device, and that it is set online correctly. Scan the console log for an I/O error message, and save it. If the error persists, give the message text to your system support.

HFMBA620   XML input data set must be sequential.

Explanation

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.

User response

None.

Programmer response

Change the XML input so it is coming from a sequential data set or a member of a PDS or PDSE and rerun the job.

HFMBA621   name=&NAM attribute error. Invalid 01 name

Explanation

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.

User response

None.

Programmer response

Change the name or rname value to be a valid 01 name for the current template.

HFMBA622   copybook=&CPY attribute error. Name cannot be matched or previously processed

Explanation

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.

User response

None.

Programmer response

If you are updating an old template (REPLACE=NO) and you haven't specified <copybooks> then you may need to rebuild this template so the copybook names can be used for the <layout>. Do this by specifying the relevant <copybook> elements. Otherwise correct the copybook name or remove the excessive <layout> elements and rerun the process.

HFMBA623   name=&NAM attribute error. Field name cannot be matched

Explanation

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

User response

None.

Programmer response

Correct the field name and rerun the process.

HFMBA628   A fully qualified member name is required

Explanation

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.

User response

None.

Programmer response

Specify a valid member name and rerun the process.

HFMBA629   Template exported to XML successfully

Explanation

Successful completion of an export function.

User response

None.

Programmer response

None.

HFMBA630   &MEMCNT members read &UPCNT Exported &REPCNT Not replaced &ERRCNT Errors

Explanation

Statistical summary message for export template function

User response

None.

Programmer response

None.

HFMBA631   &MEMCNT members read &UPCNT Exported &REPCNT Export replaced &ERRCNT Errors

Explanation

Statistical summary message for export template function

User response

None.

Programmer response

None.

HFMBA634   &MEMCNT members read &UPCNT Imported &REPCNT Import Updated &ERRCNT Errors

Explanation

Statistical summary message for import template function

User response

None.

Programmer response

None.

HFMBA635   &MEMCNT members read &UPCNT Imported &REPCNT Import replaced &ERRCNT Errors

Explanation

Statistical summary message for import template function

User response

None.

Programmer response

None.

HFMBA649   SVC99 type failed, RC rc, ERR ec, SMS RSCD ic ddname

Explanation

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

User response

For explanations of rc, ec, and ic, refer to the documentation for your current release of z/OS.

HFMBA650   SVC99 type failed, RC rc, ERR ec, INFO ic ddname

Explanation

The indicated SVC99 (allocation) operation failed.

User response

For explanations of rc, ec, and ic, refer to the documentation for your current release of z/OS.

HFMBA651   Locate macro failed, RC rc, REG0 X'xxxxxxxx'

Explanation

Unexpected return code from the LOCATE macro.

User response

For an explanation of the return code and register contents, refer to the documentation for your current release of z/OS.

HFMBA652   TIOT scan error, ddname not found

Explanation

An error occurred while scanning the z/OS control block TIOT. This is probably a Z Data Tools error.

User response

Exit Z Data Tools and rerun the function. If the problem persists, contact your system support.

HFMBA653   DSCB/JFCB read for xxxxxxx failed, RC rc

Explanation

Unexpected return code when reading the DSCB or JFCB.

User response

For an explanation of the return code, refer to the descriptions of the macros OBTAIN and RDJFCB in the documentation for your current release of z/OS.

HFMBA654   UCB scan error, RC rc, Reason Code rsn

Explanation

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

User response

For an explanation of the return code, refer to the description of the UCBSCAN macro in the documentation of your current release of z/OS.

HFMBA655   TSO Service Facility call error - RC rc, Reason Code rsn

Explanation

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

User response

For an explanation of the return code and reason code, refer to the z/OS TSO/E Programming Services.

HFMBA661   Template imported from XML successfully

Explanation

Successful completion of an import function.

User response

None.

Programmer response

None.

HFMBA665   XML error occurred on line &LINE at offset &OFFSET

Explanation

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

User response

None.

Programmer response

Look at the previous messages to determine the type of error, correct the XML line referenced and rerun the process.

HFMBA666   XML error occurred on line &LINE

Explanation

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

User response

None.

Programmer response

Look at the previous messages to determine the type of error, correct the XML line referenced and rerun the process.

HFMBA667   Line:&line value

Explanation

This message displays the line where the XML error occurred.

User response

None.

Programmer response

Look at the previous messages to determine the type of error, then correct the XML line referenced and rerun the process.

HFMBA668   Function must be run with Z Data Tools for IMS to process IMS template, views or criteria sets.

Explanation

You cannot create or update an IMS™ template view or criteria set when running the import function under the base product. It must be run from the ZDT/IMS template options if running in full screen mode or using the program HFMIMS for batch processing.

User response

None.

Programmer response

Rerun the function in a ZDT/IMS environment.

HFMBA669   Function must be run with Z Data Tools for Db2 to process Db2 templates.

Explanation

You cannot create or update a Db2 template when running the import function under the base product. It must be run from the ZDT/Db2 template options if running in full screen mode or using the program HFMDB2 for batch processing.

User response

None.

Programmer response

Rerun the function in a ZDT/Db2 environment.

HFMBA670   XML template type does not match the existing target template to be updated.

Explanation

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.

User response

None.

Programmer response

Either change the type on the <template type='value'> element to match the template to be updated or change the import to specify REPLACE=YES.

HFMBA671   Element <&ELEM.> exceeds the maximum occurrence of &NO.

Explanation

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

User response

None.

Programmer response

Correct the XML to remove the unnecessary element definitions and rerun the process.

HFMBA672   Element <&ELEM.> invalid for &TYPE template.

Explanation

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

User response

None.

Programmer response

Remove the element definition or correct the <template type='value'> to reflect the correct template type for the element.

HFMBA673   Copybook <member> element has not been found for segment=&seg.

Explanation

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.

User response

None.

Programmer response

Provide <member name='name' segname='segment'> values for all segments in the referenced DBD.

HFMBA674   One of the IMS template libraries is not a PDS or PDS/E data set.

Explanation

The associated template data set for a view or criteria set import is not a PDS or PDSE data set. 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 ZDT/IMS found either on the panels or in the options module definition.

User response

None.

Programmer response

Correct the IMS template library definitions and rerun the process.

HFMBA675   Template &TP for View or Criteria set was not found.

Explanation

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.

User response

None.

Programmer response

Ensure the associated template member can be found. This may require providing <imstp>data set name</imstp> elements to identify the location of the template member.

HFMBA676   Template &TP for View or Criteria set is corrupted.

Explanation

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

User response

None.

Programmer response

Recreate the template member or correct the template data sets (<imstp> definitions) and ensure the associated template member being loaded is a valid ZDT/IMS template.

HFMBA677   Cannot create a template of type: &type

Explanation

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.

User response

None.

Programmer response

Provide the <copybooks> elements so the template can be created.

HFMBA678   Attribute &ATTR invalid for &TYPE template.

Explanation

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

User response

None.

Programmer response

Either remove the attribute or change the template type to a type that supports the attribute referenced in the message.

HFMBA679   <dbd> element is require for &TYPE template.

Explanation

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

User response

None.

Programmer response

Provide the associated DBD name via the <dbd>name</dbd> elements and rerun the process.

HFMBA719   Change failed

Explanation

The Z Data Tools 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.

User response

Change the find or change string to avoid the problem.

HFMBA820   Key area not mapped

Explanation

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

User response

Either select a layout that can map the key field or position on a record mapped by a layout and enter FKEY with no layout.

HFMBA821   Layout not found

Explanation

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

User response

Use the "S" or "/" prefix commands to select a layout from the current listed layouts.

HFMBA822   No layout selected

Explanation

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

User response

None.

HFMBA823   Template required

Explanation

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

User response

Specify the template or copybook that you require to map the key area.

HFMBA830   Picture string invalid

Explanation

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

User response

This message is only produced if only numeric bit or Unicode fields are the target of the search or change command. Either remove the picture clause, or change the scope so character fields can be searched.

HFMBB039   FASTPROC OUTFIL statement is not supported for this type of output data set

Explanation

You ran a DSC function containing FASTPROC OUTFIL statements, and one of the following is true:
  • The input data set has fixed length records, the output data set has variable length or undefined format records, and one of the following conditions is true:
    • The output record length is undefined
    • There is a user procedure or a template being used
    • The data is packed
    • The output is a PDS(E)
  • The input data set has variable length or undefined format records, the output data set has fixed length records, and one of the following conditions is true:
    • There is a user procedure or a template being used
    • The output data set has longer records
  • The input data set is a QSAM data set with spanned records with length exceeding 32747 and the output is a VSAM data set
  • the output data set is a VSAM VRDS data set and the user requested a MOD disposition (instead of OLD)

User response

Recode the DSC function to avoid using FASTPROC OUTFIL statements. For example, you might need to recode it to use REXX statements in a REXXPROC.

HFMBB172   Error accessing CICS resource func=function Cond=condition Resp2=resp2

Explanation

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

User response

Look up the listed condition and resp2 values in the CICS Application Programming Reference or CICS System Programming Reference for further information about why the request failed.

In most cases (but not all) the listed function is the CICS command that returned the non-zero condition. Below is a list of possible values for function and the CICS command they relate to:
Function value       CICS command
INQSTART             INQUIRE
INQNEXT              INQUIRE
INQUIRE              INQUIRE
STARTBR              STARTBR
READ                 READ
ENDBR                ENDBR
WRITE                WRITE
REWRITE              REWRITE
DELETE               DELETE
OPEN                 SET (OPEN)
CLOSE                SET (CLOSE)
SET                  SET
SYNCPT               SYNCPOINT
DELETEQ              DELETEQ
ENQ                  ENQ
DEQ                  DEQ
INQGEN               INQUIRE
SET TASK             SET (TASK)
READNEXT             READNEXT
READPREV             READPREV
READUPD              READ (UPDATE)
DELQ                 DELETEQ
READQ TD             READQ (TD)

HFMBB331   Fields referenced in the TO template don't exist in the FROM template.

Explanation

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.

User response

If you are running under ISPF you should be given an option to regenerate the mapping fields and continue. For batch jobs, DSM, and DSC functions, the keyword CORRESP=YES can be used to regenerate a corresponding mapping. This way you can rerun the job with that keyword specified to override the existing mapping.

HFMBB537   Not running from APF Authorized libraries. Check STEPLIB/LINKLIST.

Explanation

Z Data Tools, after being launched from the ZCC server, detected that it is not running APF authorized, which is required.

User response

Check that the steplib or linklist libraries have been correctly authorized. See also the Z Data Tools Customization Guide.

HFMBB538   Terminating, not APF Authorized.

Explanation

Z Data Tools is shutting down. This message is issued after HFMBB537.

User response

As for HFMBB537, check that the steplib or linklist libraries have been correctly authorized. See also the Z Data Tools Customization Guide.

HFMBB573   Value data set record boundary exceeded for field FLD.

Explanation

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.

User response

Determine why the template does not correctly describe the data, resolve the problem, and then retry the operation.

HFMBB631   You can only append to CICS files - &CMD cannot be performed.

Explanation

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

User response

None.

Programmer response

None.

HFMBB632   JCL option is not supported for CICS resources.

Explanation

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

User response

None.

Programmer response

Rerun the function with the option unspecified.

HFMBC003   The Websphere MQ feature has been disabled.

Explanation

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 Z Data Tools MQ processing is disabled for this user ID.

User response

Consult with the security adminstrator to assess whether you should be allowed to run Z Data Tools MQ processing on the system.

Programmer response

None.

HFMBC250   Unix service &serv failed

Explanation

A Unix system service was called, but returned a failure. Message HFMBC251 will follow. The &serv may be one of:
MVSSIGSETUP
SIGACTION
ACCEPT
READ
WRITE
WAIT
SOCKET
SETSOCKOPT
SET KEEPALIVE
BIND
LISTEN
ASYNCIO
SPAWN
CLOSE
PASSWORD
GETPWNAM
SETUID
EXIT
ATTACH

User response

Examine the following message (HFMBC251)

HFMBC251   Unix Return value &rv, Return code &rc, reason code &RSN

Explanation

After a Unix system service call failure, this lists the return value, code and reason code.

User response

Check the meaning of the reason code by either using BPXMTEXT (if it is available on your system, you can cut and paste the &RSN code and issue, from TSO, the command BPXMTEXT reasoncode, for an explanation of the Unix system service reason code) or by consulting the manual UNIX System Services Messages and Codes.

HFMBC420   Date/time output format xxxxxxxx is not valid

Explanation

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.

User response

Refer to z/OS Language Environment Programming Services, Appendix B, "Date and time services tables" for valid picture strings supported by z/OS Language Environment.

Programmer response

None.

HFMBC421   Invalid internal data type xx specified

Explanation

The data type specified to override the field data type for date/time processing is not valid. The following are the valid data type values:
AN
Alphanumeric
B
Binary
BI
Binary
FE
External floating point
FP
Internal floating point
P
Packed decimal
PD
Packed decimal
ZD
Zoned decimal

User response

Specify one of the data types listed above.

Programmer response

None

HFMBC422   Date/time internal format is required

Explanation

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

User response

Specify the internal format value.

Programmer response

None.

HFMBC423   Invalid data type for a date/time field

Explanation

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

User response

Specify one of the appropriate data types for the date/time field.

Programmer response

None.

HFMBC424   Internal format mask is too long

Explanation

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

User response

Change the length of the internal date/time format.

Programmer response

None.

HFMBC425   Invalid internal date/time format

Explanation

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

User response

Refer to z/OS Language Environment Programming Services, Appendix B, "Date and time services tables" for valid picture strings supported by z/OS Language Environment.

Programmer response

None.

HFMBC426   Data type must be character or binary for STCK/STCKE

Explanation

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.

User response

Specify AN or BI as the internal data type for the date and time field containing STCK/STCKE values.

Programmer response

None.

HFMBC427   Field length must be 8 bytes for STCK or 16 bytes for STCKE

Explanation

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.

User response

If possible change the size of the field to the required length or change the internal format specified for the date/time field.

Programmer response

None.

HFMBC428   Internal format mask is required

Explanation

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.

User response

None.

Programmer response

Specify the internal format mask parameter on the call to CMP_DATE or CMP_TIME.

HFMBC429   Output format mask is required

Explanation

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.

User response

None.

Programmer response

Specify the output format mask parameter on the call to CMP_DATE or CMP_TIME.

HFMBC430   Unique field name too long to generate CMP_DATE or CMP_TIME function.

Explanation

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

User response

None.

Programmer response

If possible try to change the data structure so that qualification will not result in such a long name.

HFMBC431   Conversion of date/time value to lilian seconds failed.

Explanation

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

User response

None.

Programmer response

Check that the field value is valid for the internal date/time format specified.

HFMBC432   Conversion from lilian seconds to lilian days failed.

Explanation

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

User response

None.

Programmer response

Check that the field value is valid for the internal date/time format specified.

HFMBC433   Conversion from lilian days to lilian seconds failed.

Explanation

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

User response

None.

Programmer response

Check that the field value is valid for the internal date/time format specified.

HFMBC434   Base date is required

Explanation

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

User response

Specify a base date value.

Programmer response

None.

HFMBC435   Date/time output format is required

Explanation

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

User response

Specify an output format for the date/time field.

Programmer response

None.

HFMBC436   Start value for scrambling range is required

Explanation

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

User response

Specify a start value for the scrambling range.

Programmer response

None.

HFMBC437   End value for scrambling range is required

Explanation

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

User response

Specify an end value for the scrambling range.

Programmer response

None.

HFMBC438   Invalid date/time value specified

Explanation

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.

User response

Specify a valid date in the output format defined for the date/time field.

Programmer response

None.

HFMBC439   Error converting and storing a date/time value in the output field.

Explanation

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

User response

Check that there is a valid date/time value in the input field.

Programmer response

None.

HFMBC440   Range start date/time must be before the range end date/time.

Explanation

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

User response

Ensure the range start date/time is before the range end.

Programmer response

None.

HFMBC441   Scrambling type must be RANDOM or REPEAT.

Explanation

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

User response

None.

Programmer response

Specify either RANDOM or REPEAT as the value for the scrtype tag.

HFMBC442   The specified field does not contain numeric data.

Explanation

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

User response

None.

Programmer response

Specify a numeric field on the call to the STATS function or update the template to indicate the field is numeric.

HFMBC448   Date mask &MASK is invalid for field &FIELD attributes.

Explanation

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.

User response

None.

Programmer response

Change the date masks or the field length to be compatible with each other.

HFMBC443    The ODPP API is unavailable to scramble field &FIELD.

Explanation

Z Data Tools could not initialize the ODPP framework so the ODPP API is unavailable for scrambling the field name referenced.

User response

Ensure that the HFMODPP DD has been allocated, ensure that it is a single session, and check for any preceding messages that might explain why the environment could not be initialized.

Programmer response

None.

HFMBC444    Corrupt template - ODPP segment 45 not found for field &FIELD.

Explanation

This should not occur and indicates the template is corrupt.

User response

To repair the template you can attempt to export and import it.

Programmer response

None.

HFMBC445    The ODPP API is unavailable

Explanation

Z Data Tools could not initialize the ODPP framework so the ODPP API is unavailable.

User response

Ensure that the HFMODPP DD has been allocated, ensure that it is a single session, and check for any preceding messages that might explain why the environment could not be initialized.

Programmer response

None.

HFMBC515   HFMOPTS allocated to name.

Explanation

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

User response

None.

HFMBC516   Error processing HFMOPTS options file.

Explanation

Z Data Tools has encountered one or more errors while processing the options file allocated to the HFMOPTS DD statement. This message is preceded on one more error messages describing the error(s) encountered.

User response

Refer to the previous error messages related to the HFMOPTS options file. Correct the errors, and then rerun Z Data Tools.

HFMBC530    IOQ1196 Failed to lock global mutex. Is POSIX on ?

Explanation

Z Data Tools has been unable initialize the ODPP framework. The ODPP API returned the message above.

User response

The Z Data Tools Language Environment always runs with POSIX on for ODPP, so refer to the ODPP documentation for further explanation.

Programmer response

None.

HFMBC531    IOQ1094 Data Privacy Component License has expired.

Explanation

Z Data Tools has been unable to initialize the ODPP framework. The ODPP API returned the message above.

User response

Renew you ODPP license.

Programmer response

None.

HFMBC532    IOQ1086 Failed to open ODPP license key file for reading

Explanation

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

User response

Ensure you have read access for the license file.

Programmer response

None.

HFMBC533    IOQ1043 Failed to create trace file. Check path settings and write authority, etc.

Explanation

Z Data Tools has been unable to initialize the ODPP framework. The ODPP API returned the message above.

User response

Check for write access to the trace file path, disk space/quota available etc.

Programmer response

None.

HFMBC534    Data Privacy component failed. Unable to format error message, rc = &RC

Explanation

Z Data Tools has been unable to initialize the ODPP framework. The ODPP API return code is not known to Z Data Tools.

User response

Check your ODPP documentation for the return code and follow the explanation and response given.

Programmer response

None.

HFMBC857   Member &member_name Deleted.

Explanation

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

User response

None.

Programmer response

None.

HFMBC858   Member &member_name Renamed.

Explanation

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

User response

None.

Programmer response

None.

HFMBC859   Hit Enter on a member name to select the member for the enhanced search command.

Explanation

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.

User response

None.

Programmer response

None.

HFMBC860   History command deleted.

Explanation

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

User response

None.

Programmer response

None.

HFMBC861   Delete failed – ReadOnly

Explanation

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

User response

Check for other ISPF sessions that might be using your user profile data set for an enhanced search session. The enhanced search session might open the table and exit the conflicting session before attempting to retry the deletion process.

Programmer response

None.

HFMBC862   Member name exists.

Explanation

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

User response

Choose another unique name.

Programmer response

None.

HFMBC863   Replace string required.

Explanation

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

User response

Specify a replace string.

Programmer response

None.

HFMBC864   History command deleted.

Explanation

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

User response

None.

Programmer response

None.

HFMBC865   Strings required.

Explanation

The enhanced change requires both search and replace strings.

User response

Provide both search and replace strings.

Programmer response

None.

HFMBC866   &line_count line(s) in &member_count of &member_total Member(s) and &file_count of &file_total File(s)

Explanation

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

User response

None.

Programmer response

None.

HFMBC867   &change_count changes made in &member_count Members &file_count Files.

Explanation

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

User response

None.

Programmer response

None.

HFMBC868   Changes failed RC=&rc.

Explanation

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

User response

Refer to the associated messages that detail why the change couldn’t be performed is displayed.

Programmer response

None.

HFMBD520   Invalid value for data set, prefix or suffix name: &dsn

Explanation

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

User response

Correct the name so it represents a valid z/OS data set name. Each qualifier must be a maximum of 8 characters, and the overall length must not exceed 44.

Programmer response

None.

HFMBD521   Invalid value for member name: &member_name

Explanation

An invalid partitioned member name has been specified.

User response

Correct the member name and retry the operation.

Programmer response

None.

HFMBD522   Invalid generic output data set name with non generic input: &dsn

Explanation

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.

User response

Remove the generic characters in the name of the output data set that cannot be derived from the input data set name.

Programmer response

None.

HFMBD523   Input and output data set names are the same: &dsn

Explanation

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.

User response

Correct the output prefix or name so a different name is generated to the input data set.

Programmer response

None.

HFMBD524   Duplicate input or output data set name specified or generated: &dsn

Explanation

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

User response

Check your input and output prefixes or data set specifications and remove the specifications that would result in the same output data set.

Programmer response

None.

HFMBD525   Output mask invalid. Input data set:&dsn Output Prefix:&prefix. Invalid mask:&mask

Explanation

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

User response

Remove the generic characters from the &mask value.

Programmer response

None.

HFMBD526   Resultant output data set name &odsn invalid. Input data set: &idsn

Explanation

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.

User response

Review the input and output prefix and suffix values based on the output data set name that is shown in the message, and correct them so a valid output data set name is generated.

Programmer response

None.

HFMBD527   No data sets matched the qualifier: &prefix.

Explanation

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

User response

Add a .** to the end of the &prefix value that is provided. Or correct the qualifier to match existing data sets.

Programmer response

None.

HFMBD528   HFMSREF - Required parameter not specified FUNC=&function, FCODE=&code RNAME=&reference_name

Explanation

The HFMSREF exec was called with an invalid parameter value.

User response

One of the references has not been specified by the calling EXEC. Check the parameters. If the values are missing, provide the values. If the calling EXEC is an HCL exec, report this to HCL Support.

Programmer response

None.

HFMBD529   HFMSREF - Function value invalid FUNC=&function must be GREF or SREF

Explanation

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

User response

The valid values are GETREF, GREF, GR, SAVEREF, SREF, SR. Correct the calling exec and rerun. If the calling EXEC is an HCL exec, report this to HCL Support.

Programmer response

None.

HFMBD530   The GETREF command was entered and no matching reference value can be found for the value or no references have been saved for the current function.

Explanation

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

User response

Issue the command with a valid reference. Or ensure you have used the SAVEREF command to save references for this function before a GETREF is attempted.

Programmer response

None.

HFMBD531   This is not a valid enhanced search report.

Explanation

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.

User response

None. The command only works in search reports that are produced by the Z Data Tools enhanced search process.

Programmer response

None.

HFMBD532   Invalid enhanced search parameter value &parm_value

Explanation

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

User response

Examine the command by comparing with the syntax that is described in the user's guide for the enhanced search command. Correct the invalid parameter value.

Programmer response

None.

HFMBD533   Report Converted

Explanation

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

User response

None.

Programmer response

None.

HFMBD534   String required after the operator

Explanation

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.

User response

Correct the syntax and retry.

Programmer response

None.

HFMBD535   To Column value cannot be less than the From Column value.

Explanation

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

User response

Correct the range values and retry.

Programmer response

None.

HFMBD536   DD name &DD invalid

Explanation

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 (*,%).

User response

Correct the syntax and retry.

Programmer response

None.

HFMBD600   The SAVEREF command is not available for this function.

Explanation

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

User response

If the function that you are working on is a common function and it needs to be supported, contact HCL Support to raise a new requirement to support the function.

Programmer response

None.

HFMBD601   The GETREF command is not available for this function.

Explanation

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

User response

If the function that you are working on is a common function and it needs to be supported, contact HCL Support to raise a new requirement to support the function.

Programmer response

None.

HFMBD602   No function input field values have been previously saved.

Explanation

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

User response

You must issue the SAVEREF command before you issue a GETREF command for any function or panel where it is supported.

Programmer response

None.

HFMBD603   No saved input field values for this reference name

Explanation

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

User response

Issue a GETREF command without a name that lists the current references. Select a name from a list of saved references.

Programmer response

None.

HFMBD604   &name saved.

Explanation

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

User response

None.

Programmer response

None.

HFMBD605   Save cancelled.

Explanation

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

User response

None.

Programmer response

None.

HFMBD607   &name Retrieved.

Explanation

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

User response

None.

Programmer response

None.

HFMBD608   &name Replaced.

Explanation

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

User response

None.

Programmer response

None.

HFMBD612   New name same as the old name.

Explanation

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

User response

Correct the new name so it is different from the old name.

Programmer response

None.

HFMBD613   New name exists.

Explanation

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

User response

Enter a new name that does not exist.

Programmer response

None.

HFMBD614   Invalid attributes for HFMREFTB file must be fixed 80.

Explanation

The data set that is allocated to the HFMREFTB 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.

User response

Enter a new name that does not exist.

Programmer response

None.

HFMBE004   Expressions requiring REXX cannot be used for redefines criteria

Explanation

Redefines criteria expressions are restricted to FASTREXX. Expressions requiring REXX (expressions that have arithmetic or REXX functions, such as SUBSTR, WORD) or HFM external functions that are not supported for FASTREXX cannot be used in the criteria.

Programmer response

Enter an expression that is supported by FASTREXX.
  • See External REXX functions for a list of the external functions that are available. Look for "Can be used in FASTREXX" to determine whether the function can be used.
  • REXX arithmetic is not supported in FASTREXX.

HFMBE005   CR,CF commands are not valid for a level 1 field.

Explanation

The prefix commands CF and CR during a template edit session are not valid for the level 1 field.

Programmer response

Issue the prefix command against fields that have a REDEFINES clause or fields that are the target of a REDEFINES clause.

HFMBE052   Template data invalid for load Rsn=nnn

Explanation

The Z Data Tools template is invalid. It may have been corrupted by editing it outside of Z Data Tools.

User response

If this is not the case, then please report the problem to your Support Representative, stating the Reason Code.

HFMBE094   COBOL compile failed with Language Environment RC &RC and RSN &RSN

Explanation

When Z Data Tools invokes COBOL compiler Version 5 (and above), it may terminate with a Language Environment Abend Code which may be found in the Language Environment publication. If Abend code is 4093 and Reason code X'1C' or 28, then there is insufficient storage to run the compiler.

COBOL Version 5 requires at least 100MB of storage.

User response

The Language Environment abend and reason codes can be found in z/OS Language Environment Run-Time Messages manual.

HFMBE351   Start position beyond end of file.

Explanation

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.

User response

To process records, you must specify a starting position whose value is lower than that of the KEY, RBA, or record number of the last record.

Programmer response

None.

HFMBE491   No Db2 TABLE matches the value entered. It is possible a Db2 object (eg view) that matches the name entered exists - however the selected Db2 utility supports Db2 tables ONLY.

Explanation

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.

User response

Ensure that the Db2 object name specified is a Db2 table.

HFMBE719   Change failed

Explanation

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

User response

The explanation of the associated return code can be found in FCH (Find/Change).

HFMBE805   SMF logging error. Value returned by BPX1SMF: RC=&rc Reason Code=&RSN(Dec)

Explanation

Z Data Tools 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.

User response

This error usually indicates a set-up problem. Possible reason for an auditing failure to SMF are:
  1. The userid does have READ access to the SAF FACILITY class profile BPX.SMF.
  2. The HFM0POPT module does not have a valid number specified for the SMFNO parameter.
Consult the systems programmer for assistance in resolving the cause of the error.

HFMBE808   CCSID not valid

Explanation

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

User response

Change the CCSID to one that is known by this Z/OS system.

HFMBE895   CCSID display off

Explanation

The CCSID column is not displayed in single formatting.

User response

None

HFMBE898   CCSID display on

Explanation

The CCSID column is displayed in single formatting.

User response

None

HFMBE991   Not selected record

Explanation

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.

User response

Identify the record containing the field to be mapped by positioning the record at the top of the screen or position the cursor on the record when the FMAP command is entered.

HFMBE992   No field selected

Explanation

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

User response

Reissue the FMAP command and select a field from the list supplied in the Field Selection List panel.

HFMBE993   No template provided

Explanation

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

User response

Supply Template or Copybook details on the FMAP Copybook or Template panel

HFMBE994   Data may be truncated

Explanation

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

User response

None

HFMBE998   No column selected

Explanation

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

User response

Enter the FMAP command and select the column to be mapped on the Field Selection List panel.

HFMBE999   Field reference invalid

Explanation

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

User response

Specify the correct field reference in the FMAP command.

HFMBF003   Not enough space.

Explanation

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.

User response

Remove one or more characters using HEX ON to see the characters in UNICODE.

HFMBF123   Converted UNICODE data too big for receiving field. Field name length lllll.

Explanation

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

User response

Increase the size of the receiving field in the template by either changing the copybook and regenerating the template or editing the dynamic template and changing the field size.

HFMBF124   Return code rc, reason code rsn from CUNLCNV routine. Field name.

Explanation

The routine CNVLCNV could not convert the field name.

User response

For an explanation of the return code and reason code refer to the z/OS V1R11.0 Support for Unicode Using Unicode Services.

HFMBF126   Not valid for migrated

Explanation

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

User response

RECALL the data set and reissue the command if required.

HFMBF427   Program Binder does not recognize member as a Load Module / Program Object. Function=&fc RC=&rc reason=&rsn.

Explanation

The Z Data Tools 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.

User response

Refer to the manual SA22-7644-xx MVS™ Program Management: Advanced Facilities for an explanation of the Binder API return codes and reason codes.

HFMBF434   The module member does not contain any CSECT names.

Explanation

The Z Data Tools View Load Module utility found no CSECT names in the module member and therefore cannot provide any information.

User response

None.

HFMDJ999   Z Data Tools problem - message nnnn not found in table

Explanation

Z Data Tools cannot find the message number nnnn in the message table. This is probably a Z Data Tools error.

User response

Contact your system support.