SET LONGCUNAME command

Controls whether a short or long CU name is displayed.

Read syntax diagramSkip visual syntax diagramSETLONGCUNAME ONOFF ;
ON
Specifies that a long CU name is displayed.
OFF
Specifies that a short CU name is displayed. The short CU name is displayed in the session panel header, source window header area, and the Source Identification Panel.

Usage notes

  • You can enter the SET LONGCUNAME at any time, but it applies only to C, C++, and Enterprise PL/I programs. If you compiled your program with one of the following compilers and it is running in the following environment, this command has no effect.
    • Enterprise PL/I for z/OS®, Version 3.6 or later
    • Enterprise PL/I for z/OS, Version 3.5, compiler with the PTFs for APARs PK35230 and PK35489 applied
  • The CU name for programs compiled with C, C++, or Enterprise PL/I (before Enterprise PL/I for z/OS, Version 3.6) compilers can have one of the following forms:
    • Fully qualified partitioned data set name and member name
    • A sequential file name
    • An HFS or zFS path and file name

    These forms can result in long CU names that are truncated in the session panel header, which makes it difficult for you to identify the CU.

    For these forms of compile unit names, z/OS Debugger displays short names in one of the following manners:

    • For PDS file names, the short name is only the member name
    • For sequential file names, the short name is the lowest level qualifier (name segment)
    • For HFS or zFS file names, the short name is the file name, without path name
  • z/OS Debugger commands affected by the LONGCUNAME setting: QUERY LOCATION, SET SOURCE, and AT ENTRY. All the other commands continue to require the long form of the CU name. For example, if you use the short name with the AT command (AT ARRAY3 ::> 'ARRAY3' :> 10), z/OS Debugger displays an error message and does not set the breakpoint. However, if you enter the command AT ENTRY ARRAY3 ::> ’ARRAY3’ :>ARRAY3, z/OS Debugger sets the breakpoint or defers setting the breakpoint until the entry point is known to z/OS Debugger.
  • You cannot use the SET LONGCUNAME command in remote debug mode.

Examples

  • If the CU name is SMITH.TEST.SRC(ARRAY3), the short name is ARRAY3.
  • If the CU name is SMITH.TEST.SOURCE.ABCD, the short name is ABCD.
  • If the CU name is /testenvir/applications/cicsprograms/project1/prog2.cpp, the short name is prog2.cpp.