LOADGO command operands

(data_set)

specifies the names of one or more object modules, load modules and /or program objects to be loaded and executed. The names can be data set names, names of members of partitioned data sets, or both (see the data set naming conventions). When you specify more than one name, the names must be enclosed within parentheses and separated from each other by a standard delimiter (blank or comma).

‘parameters’

specifies any parameters that you want to pass to the program to be executed.

PRINT(data_set_name | *) | NOPRINT

PRINT(data_set_name | *): specifies the name of the data set that is to contain the listings produced by the LOADGO command. If you omit the data set name, the generated data set is named according to the data set naming conventions. You can substitute an asterisk (*) for the data set name, if you want to have the listings displayed at your terminal. If you specify the MAP operand, then PRINT is the default.
NOPRINT: specifies no listings are to be produced. This operand suppresses the MAP operand. If both PRINT and NOPRINT are omitted and you do not use the MAP operand, then NOPRINT is the default.

AMODE(24 | 31 | 64 | ANY | MIN)

specifies the addressing mode for the module to be loaded. If the AMODE operand is not specified, AMODE defaults to the AMODE of the main entry point. Valid AMODE values are:

24

indicates that the module is invoked in 24-bit addressing mode.

31

indicates that the module is invoked in 31-bit addressing mode.

64

indicates that the module is invoked in 64-bit addressing mode.

ANY

indicates that the module is invoked in either 24-bit or 31-bit addressing mode.

MIN

causes the binder to set the AMODE to the most restrictive AMODE of all control sections in the module. In this respect, 24 is more restrictive than 31, which is more restrictive than ANY.

The MIN keyword is used only to control binder processing. It assists the binder in determining the resultant AMODE of the module. However, MIN is never used as an AMODE itself and will not appear in the directory entry of the resultant load module or program object.

For more information see z/OS MVS Program Management: User's Guide and Reference.

RMODE(24 | ANY | SPLIT)

specifies the residence mode for the module to be loaded. If all control sections are not specified as RMODE(ANY), RMODE defaults to 24. If any section of the load module has an RMODE(24), RMODE defaults to 24. Valid RMODE values are:

24: to indicate the module must reside below the 16 MB line
ANY: to indicate the module can reside anywhere below the 2GB bar in virtual storage
SPLIT: to indicate that the program object is to be split into two segments according to the RMODE of the CSECTs. SPLIT is supported only for PM2 or PM3 format program objects.

LIB(data_set)

specifies names of one or more library data sets that are to be searched to find modules referred to by the module being processed (that is, to resolve external references).

BINDER | NOBINDER

BINDER: specifies that MVS™ use binder services for this load module or object module rather than the loader service program. The binder can be used for to read modules stored in a PDS and program objects in a PDSE or Unix file. BINDER is the default.
NOBINDER: specifies that MVS not use binder services for this object module; the loader service program is used to process the object module(s) into load module(s).

CASE(UPPER | MIXED)

UPPER: specifies that the binder translates to uppercase all lowercase names found in input modules, binder control statements, and LOADGO parameters. UPPER is the default.
MIXED: specifies that the binder respect uppercase and lowercase names found in input modules, control statements, call parameters, and LOADGO parameters. If MIXED is specified, the binder treats two strings differently if any character in one string is a different case than the corresponding character in the second string. binder keywords are always translated to uppercase.

COMPAT(MIN | CURR | CURRENT | LKED | PM1 | PM2 | PM3 | PM4 | release)

specifies binder compatibility level.

MIN

indicates the oldest level (PM2 or higher) that supports the features in the object. This is the default.

CURRENT

indicates the latest level know to the binder.

CURR

is the abbreviation of CURRENT and has the same specification.

LKED

specifies that the binder process certain options, such as AMODE/RMODE and reusability, in a manner compatible with the linkage editor.

PM1

specifies that the binder create a PM1-level program object or load module.

PM2

specifies that the binder create a PM2-level program object.

PM3

specifies that the binder create a PM3-level program object. PM3 is the default.

PM4

is the minimum level that can be specified. A value of 64 is specified on the AMODE option. Input modules contain 8-byte address constants and names longer than 1024 characters.

release

OSV2R8 through OSV210 (same as PM3)
ZOSV1R1 and ZOSV1R2 (same as PM3)
ZOSV1R3 and ZOSV1R4 (same as PM4)
ZOSV1R5 and ZOSV1R6 (adds RMODE 64 for WSA)
ZOSV1R7 (adds compression and relative/immediate hardware instruction references across elements)

FILL(fill_byte)

specifies to the binder the byte value to be used to initialize uninitilalized storage areas in the loaded program. This must be two hexadecimal digits or the word NONE.

HOBSET(NO | YES)

NO: specifies that the binder NOT set the high-order bit (HOB) in V-type adcons according to the AMODE of the target entry point. NO is the default.
YES: specifies that the binder set the high-order bit (HOB) in V-type adcons according to the AMODE of the target entry point.

LINECT

specifies the number of lines (including heading and blank lines) contained on each page of the binder listing. The valid range is 24-200 and 0. Zero indicates a single, indefinitely long page, and values of 1-23 are forced to 24; however, there are always page ejects at the beginning of the binder listing and the start of the map, cross reference (XREF), and summary reports. LINECT defaults to 60 lines.

allows you to control the type of information included in the SYSPRINT data. LIST is valid for both the linkage editor and the binder. LIST, with no value, is equivalent to LIST (SUMMARY), and NOLIST is equivalent to LIST(OFF).

OFF: indicates that only messages will be printed. In a batch environment, LIST(OFF) is equivalent to NOLIST.
STMT: indicates that messages and control statements to be printed. In a batch environment, LIST(STMT) is equivalent to LIST.
NOIMPORT: produces the same output as SUMMARY except without IMPORT control statements.
SUMMARY: indicates that messages, control statements, and a load summary report (including processing options and module attributes) are to be printed.
ALL: indicates that all input activity (whether initiated by binder service calls or control statements) and the load or save summary be logged.

PLILIB

specifies the partitioned data set named SYS1.PL1LIB is to be searched to locate external symbols referred to by the module being processed.

PLIBASE

specifies the partitioned data set named SYS1.PLIBASE is to be searched to locate external symbols referred to by the module being processed.

PLICMIX

specifies the partitioned data set named SYS1.PLICMIX is to be searched to locate external symbols referred to by the module being processed.

FORTLIB

specifies the partitioned data set named SYS1.FORTLIB is to be searched to locate external symbols referred to by the module being processed.

COBLIB

specifies the partitioned data set named SYS1.COBLIB is to be searched to locate external symbols referred to by the module being processed.

TERM | NOTERM

TERM: specifies that you want any error messages directed to your terminal and the PRINT data set. If both TERM and NOTERM are omitted, then TERM is the default.
NOTERM: specifies that you want any error messages directed only to the PRINT data set.

RES | NORES

RES: specifies the link pack area is to be searched for load modules (referred to by the module being processed) before the specified libraries are searched. If both RES and NORES are omitted, then RES is the default. If you specify the NOCALL operand, the RES operand is not valid.
NORES: specifies the link pack area is not to be searched to locate modules referred to by the module being processed.

MAP | NOMAP

MAP: specifies a list of external names and their real storage addresses are to be placed on the PRINT data set. This operand is ignored when NOPRINT is specified.
NOMAP: specifies external names and addresses are not to be contained in the PRINT data set. If both MAP and NOMAP are omitted, then NOMAP is the default.

CALL | NONCAL | NOCALL | NCAL

CALL | NONCAL: specifies the data set specified in the LIB operand is to be searched to locate load modules referred to by the module being processed. CALL is the default.
NOCALL | NCAL: specifies the data set specified by the LIB operand is not to be searched to locate modules that are referred to by the module being processed. The RES operand is not valid when you specify NOCALL.

LET(sev_code)

specifies a severity code, which if exceeded, will prevent execution of the module. The severity code is the aggregate error level of all calls to the binder. Valid values for severity code are 0, 4, 8, and 12. If LET is specified, it defaults to LET(8); if LET is not specified it defaults to LET(4). NOLET is equivalent to LET(0).

MSGLEVEL

specifies the severity level below which messages are not displayed. Valid severity levels are 0, 4, 8, and 12. If a message has a severity lower than the level indicated here, it is not printed, written to either print or terminal files, or passed to the messages exit.

WKSPACE(value_1[,value_2])

specifies the maximum amount of user's virtual storage available to the binder below and above 16 MB. You do not need to include this operand unless you have special virtual storage considerations such as the virtual storage between two concurrent applications needs to balance. If coded, a minimum of WKSPACE(96,1024) is suggested for all binder operations.

value_1: indicates the maximum amount (in KB) of user's virtual storage available to the binder below 16 MB in virtual storage. This value is optional; however, be certain to code a comma ( , ) if only value_2 is specified.
value_2: indicates the maximum amount (in KB) of user's virtual storage available to the binder above 16 MB in virtual storage. This value is optional; however, be certain to code a comma ( , ) if value_1 is not also specified.

SIZE(integer)

specifies the size, in bytes, of dynamic real storage that can be used by the loader. If this operand is not specified, then the size defaults to the size specified by your system programmer.

EP(entry_name)

specifies the external name for the entry point to the loaded program. If the entry point of the loaded program is in a load module, you must specify the EP operand. The maximum value length of EP has been extended from 8 characters to 64 characters.

NAME(program_name)

specifies the name that you want assigned to the loaded program.

XREF | NOXREF

XREF: A cross-reference list of external symbol usage is written to the print destination. A map of symbol locations must be requested separately if desired.
NOXREF: No cross-reference of external symbol usage is produced.

LISTPRIV(YES | NO)

Include a list of unnamed (private code) sections.

Note: This is a diagnostic tool to detect unnamed sections, which can cause problems in rebinding. If any unnamed sections are found when running with LISTPRIV(YES), a level 8 error message will be produced.