The parameters, keywords, and variables of the CRTBNDRPG command are listed below. The same information is available online. Enter the command name on a command line, press PF4 (Prompt) and then press PF1 (Help) for any parameter you want information on.
See Using the application development tools in the client product for information about getting started with the client tools.
The path name can be either absolutely or relatively qualified. An absolute path name starts with '/'; a relative path name starts with a character other than '/'.
If absolutely-qualified, the path name is complete. If relatively-qualified, the path name is completed by appending the job's current working directory to the path name.
The SRCMBR and SRCFILE parameters cannot be specified with the SRCSTMF parameter.
Specifying DFTACTGRP(*YES) allows ILE RPG programs to behave like OPM programs in the areas of override scoping, open scoping, and RCLRSC.
ILE static binding is not available when a program is created with DFTACTGRP(*YES). This means that you cannot use the BNDDIR or ACTGRP parameters when creating this program. In addition, any call operation in your source must call a program and not a procedure.
DFTACTGRP(*YES) is useful when attempting to move an application on a program-by-program basis to ILE RPG.
If ACTGRP(*CALLER) is specified and this program is called by a program running in the default activation group, then this program will behave according to ILE semantics in the areas of file sharing, file scoping and RCLRSC.
DFTACTGRP(*NO) is useful when you intend to take advantage of ILE concepts; for example, running in a named activation group or binding to a service program.
Statement_Number = source_ID * 1000000 + source_SEU_sequence_number
SEU Sequence Numbers are shown on the left-most column of the listing.
Statement Numbers are shown on the right-most column of the listing; these
numbers are used when debugging using statement numbers.
CODE/400 uses this file to provide error feedback integrated with the CODE/400 editor. An Event File is normally created when you create a module or program from within CODE/400.
If the key contains any characters which are not invariant over all code pages, it will be up to the user to ensure that the target system uses the same code page as the source system, otherwise the key may not match and the decryption may fail. If the encryption key must be entered on systems with differing code pages, it is recommended that the key be made of characters which are invariant for all EBCDIC code pages.
If you want to use the SRTSEQ and LANGID parameters to determine the alternate collating sequence, you must also specify ALTSEQ(*EXT) on the control specification.
Valid values for this parameter change every release. The possible values are:
Valid values depend on the current version, release, and modification level, and they change with each new release. If you specify a target-release that is earlier than the earliest release level supported by this command, an error message is sent indicating the earliest supported release.
The directory name can be qualified with one of the following library values:
The compiler will search the directories specified here if the relatively specified copy files in the source program can not be resolved by looking in the current directory.If the copy file cannot be found in the current directory or the directories specified in the INCDIR parameter, the directories specified in the RPGINCDIR environment variable will be searched, followed by the directory containing the main source file.
Specifies the path name of the stream file to contain the generated program interface information specifed on the PGMINFO option.
The path name can be either absolutely or relatively qualified. An absolute path name starts with '/'; a relative path name starts with a character other than '/'.
If absolutely-qualified, the path name is complete. If relatively-qualified, the path name is completed by appending the job's current working directory to the path name.
This parameter can only be specified when the PGMINFO parameter has a value other than *NO.
The possible options are:
The possible library values are:
The path name can be either absolutely or relatively-qualified. An absolute path name starts with '/'; a relative path name starts with a character other than '/'.
If absolutely-qualified, the path name is complete. If relatively-qualified, the path name is completed by appending the job's current working directory to the path name.