The epname is 1 to 8 alphanumeric characters and must begin with an EBCDIC letter (A-Z) or national character ($, #, @). Lowercase alphabetic characters are accepted and treated as uppercase.
The name is 1 to 8 alphanumeric characters and must begin with an EBCDIC letter (A-Z) or national character ($, #, @). Lowercase alphabetic characters are accepted and treated as uppercase.
Default: HBB3310
The groupname specifies the type of control blocks to be associated with each type of data being defined by this DATA statement. Do not reference an area or structure as a groupname if the AREA or STRUCTURE parameter references another group data type. If an attempt is made to establish such a relationship, IPCS will detect an error, and the group data type associated with the explicitly-referenced group will be used instead.
The groupname is 1 to 31 alphanumeric characters and must begin with an EBCDIC letter (A-Z) or national character ($, #, @). Lowercase alphabetic characters are accepted and treated as uppercase.
The modelname is 1 to 8 alphanumeric characters and must begin with an EBCDIC letter (A-Z) or national character ($, #, @). Lowercase alphabetic characters are accepted and treated as uppercase.
The scanname is 1 to 8 alphanumeric characters and must begin with an EBCDIC letter (A-Z) or national character ($, #, @). Lowercase alphabetic characters are accepted and treated as uppercase.
Default Value: ALL
dialogname - textThe text is 1 to 60 alphabetic characters and must be enclosed in single quotation marks. Uppercase and lowercase letters are accepted; both cases are shown on the panel.
If a parmlib member contains a CLIST, the system considers the CLIST as part of the member. If a CLIST generates an END statement, the CLIST generating the END statement, any other CLIST invoked by the currently embedded member, and the currently embedded member are ended.
An END statement is useful to prevent processing of a block of statements that you want IPCS to ignore for the time being.
If VERB(verbname) is also specified, the exit routine will also be invoked by the VERBEXIT verbname subcommand. If ABSTRACT is also specified, the exit routine will also be invoked through the IPCS MVS Dump Component Data Analysis panel of the IPCS dialog.
EXIT EP(ISGDCONT) ANALYZEIf VERB(verbname) is also specified, the exit routine will also be invoked by the VERBEXIT verbname subcommand.
The name is 1 to 31 alphanumeric characters and must begin with an EBCDIC letter (A-Z). Lowercase alphabetic characters are accepted and treated as uppercase.
EXIT EP(IEAVTRCA) CBSTAT(ASCB)See the post-formatting exit routine in z/OS MVS IPCS Customization.
For the SUMMARY subcommand, the system invokes the FORMAT exit routines in the order they are specified in BLSCECT and its embedded parmlib members.
The name is 1 to 31 alphanumeric characters and must begin with an EBCDIC letter (A-Z). Lowercase alphabetic characters are accepted and treated as uppercase.
If VERB(verbname) is also specified, the exit routine will also be invoked by the VERBEXIT verbname subcommand.
EXIT EP(IEAVG701) CBSTAT(TCB)If ANALYZE, ASCB, or TCB is also specified, the exit routine will also be invoked by the ANALYZE, ASCBEXIT, or TCBEXIT subcommand.
The verbname is 1 to 8 alphanumeric characters and must begin with an EBCDIC letter (A-Z) or national character ($, #, @). Lowercase alphabetic characters are accepted and treated as uppercase. Each verbname must be unique. It must not duplicate another verb name on an EXIT statement or a dialog name on a DIALOG statement specified in BLSCECT and its embedded parmlib members.
To specify more than one verbname for the same EP pgmname, code a separate EXIT statement for each verbname.
EXIT EP(IGVSFMAN) VERB(VLFDATA)verbname - textThe text is 1 to 60 alphabetic characters and must be enclosed in single quotation marks. Uppercase and lowercase letters are accepted; both cases are shown on the panel. If an exit routine is invoked by multiple verb names, the first verb name associated with the exit in the parmlib member(s) is used on the panel.
The following example is for VTAM®.
EXIT EP(VTAMMAP) AMASK(X'00FFFFFF')Default Value: X'7FFFFFFF'
Default Value: ALL
The name is 1 to 8 alphanumeric characters and must begin with an EBCDIC letter (A-Z) or national character ($, #, @). Lowercase alphabetic characters are accepted and treated as uppercase.
The text is 1 to 32,767 alphanumeric characters and must be enclosed in single quotation marks. Mixed upper and lowercase alphabetic characters will be accepted and passed as is to the routine.
The membername is 1 to 8 alphanumeric characters and must begin with an EBCDIC letter (A-Z) or national character ($, #, @). Lowercase alphabetic characters are accepted and treated as uppercase.
Default Value: IPCS
NOTE statement syntax is identical to the syntax of the IPCS NOTE subcommand.
| SUFFIX Value | Maximum Prefix Length |
|---|---|
| COUNT0 | 1 to 26 characters |
| COUNT1 | 1 to 26 characters |
| COUNT1NAME | 1 to 25 characters |
| CPU | 1 to 29 characters |
| DUALCOUNT | 1 to 21 characters |
| NAME | No longer than 31 characters minus the length of the prefix |
| UNIT | 1 to 26 characters |
Some examples are the suffixes of 34C in the symbol JSABA34C, of 1A in PGT1A, and of 5F in TCB75F.
Examples are: CVT, GDA, or PRIVATE.
list cvtlist cvt structure(cvt)Default: SYS1.DDIR
Use the TSO statement when the TSO/E command, CLIST name, or REXX exec name duplicates the name of a BLSCUSER statement. A TSO/E command with a name that does not duplicate a BLSCUSER statement name can be specified without TSO before it.
A CLIST that generates BLSCUSER statements can also be specified in the parmlib member; place a percent sign (%) before the CLIST name.
TSO/E commands and REXX execs may use the TSO/E stack to leave BLSCUSER statements for processing after the command or exec ends processing.
TSO/E commands supplied with IPCS, IPCS primary commands and IPCS subcommands try to lighten this burden in two ways: Some keywords that you tend to use often, e.g. CHARACTER, support explicit, short aliases, C in this case. All keywords can be truncated, entering just enough of their characters to make what you have entered unambiguous. For example, LENGTH is a keyword accepted on many subcommands. Entering LEN instead of LENGTH is currently unambiguous on them all. If you are composing a command procedure that you hope will remain useful for a long time, do not truncate keywords in it. As IPCS responds to new demands, new keywords can be introduced that make truncations ambiguous. Support for truncation is solely intended to make manual entry of commands and writing command procedures intended for brief use faster and easier.