The programmer's name can be specified in the command string for follow-up processing for the local system and for the partner system, if this is also an openFT (z/OS). A separate value for the programmer's name can be specified in each of the four command strings for follow-up processing provided in the NCOPY command (local system and partner system, both for successful and unsuccessful transfers). openFT uses the specified programmer's name in the following locations:
in the JOB statement of the jobs for follow-up processing; the following applies here:
this specification is used automatically in the jobs that openFT creates by default when the computing center does not provide its own defaults
this specification can also be used in jobs for follow-up processing predefined by the computing center; this is described in more detail in the manual "openFT (z/OS) - Installation and Operation"
in the JOB statement of the job for printing out the result list; the following applies here:
this specification is used automatically in the job that openFT creates by default when the computing center does not provide its own defaults
this specification can also be used in the job predefined by the computing center for printing the result list; this is described in more detail in the manual "openFT (z/OS) - Installation and Operation"
as a substitute value for the variable PGRN or PGRX, which can be used in the statements for follow-up processing
as a substitute value for the variable PGRN or PGRX, which can be used in the message texts predefined by the computing center for asynchronous messages once a file transfer has been completed; this is described in more detail in the manual "openFT (z/OS) - Installation and Operation"
The programmer's name must be specified as a subcommand within the command string for follow-up processing with the keyword PGRN=. The following additional conditions must be observed:
The subcommand "PGRN=value" may be used only once within a string. If this is not the case, the analysis is terminated, i.e. any follow-up processing is not started, and no value for the programmer's name is saved for further use.
The "value" specification must come directly after the character "=" and ends with the first blank or, if it is within quotes, with the last quote in the substring. There must be no other character except the blank between the end of the value determined in this way and the end of the substring (";" or end of string); otherwise, the analysis is aborted (see above).
Each quote which occurs must be doubled, since follow-up processing strings are themselves enclosed in quotes (c string).
The value specifying the programmer's name must comply with the following IBM syntax rules:
Maximum length 20 characters, excluding enclosing quotes
The specification must be enclosed in quotes when metacharacters are used; exception: hyphen, leading periods or embedded periods.
Each quote which is part of the name must be doubled.
If the partner system is not an openFT for z/OS (specification REMOTE=*BS2000/*ANY in the NCOPY command), no specification may be made for the programmer's name in the command string for follow-up processing in the partner system, since these partner systems do not support the specification of a programmer's name.
Of these rules, openFT checks only the length of the value specified for the programmer's name. If it is longer than the maximum permissible length, the analysis is aborted (see above).
Specifications for the programmer's name which have the wrong syntax, and particularly the wrong number of quotes, cause an error in jobs to which the programmer's name has been assigned.s
Examples
The following specifications have a valid syntax (the string "...;" here represents any sequence of TSO commands or JCL statements):
SUCC='...; //* PGRN=TEST-1' (1) SUCC='...; //* PGRN=.TEST' (1) SUCC='...; //* PGRN=TEST.1' (1) FAIL='...; //* PGRN=''TEST 1''' (2) FAIL='...; //* PGRN=''TEST/1''' (2)
|
|
Explanations: |
(1) | Hyphens, leading periods and embedded periods as part of the programmer's name do not require quotes. |
(2) | If there are metacharacters in the specification of the programmer's name (here: blank, slash, period at the end), the specification must be enclosed in quotes.Since the follow-up string is also enclosed in quotes, each of these quotation marks must be doubled. |
(3) | Even when the specification of the programmer's name contains a quotation mark (here: O'REILLY), the specification must be enclosed in quotes; the quotation mark itself must be doubled (i.e. 'O''REILLY').Since the follow-up string is also enclosed in quotes, each of these quotation marks must be doubled. |