z/OS MVS JCL Reference
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Subparameter definition

z/OS MVS JCL Reference
SA23-1385-00

value
Required. A subsystem-defined parameter (maximum = 127) to pass from a spooling product to a despooler.
The following considerations apply when you supply the value a functional subsystem requires:
Characters valid when enclosed in apostrophes
  • You may include any EBCDIC text characters in an FSSDATA parameter value if you enclose the value in apostrophes. See Character Set in topic 4.2 for a list and description of valid EBCDIC text characters.
  • You must enclose the value in apostrophes if it contains a blank.
  • The system preserves trailing blanks you include as part of a value you enclose in apostrophes. For example, if you specify
    FSSDATA='SUNDAY   '

    the parameter value for the FSSDATA keyword is eight (8) characters, and a functional subsystem may deem it to be different from

    FSSDATA='SUNDAY'

    (6 characters) or

    FSSDATA='SUNDAY  '

    (7 characters).

  • To code an apostrophe as part of the value, code two apostrophes, as well as enclosing the entire value in single apostrophes. Example:
    //OUT1     OUTPUT FSSDATA='New Year''s Day'
Characters not requiring enclosing apostrophes
Apostrophes are optional when "value" consists only of:
  • Uppercase alphanumeric characters
  • National characters @, $, and #
  • Period (.)
  • Asterisk (*). However, an asterisk followed by a period indicates a referral; *. is NOT allowed as the first two characters of the value
  • Ampersand (&). An ampersand referring to a symbolic is substituted. Two consecutive ampersands are not substituted; they will result in a single ampersand as part of the value
  • Plus sign (+)
  • Hyphen(-)
  • Slash (/)
Characters you may not enclose in aphstrophes
Do not enclosed symbolic parameters within apostrophes. The system will not resolve them.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014