The following table describes the things to consider when using the ACCEPT command.
| Topic | Usage Notes |
|---|---|
| Specifying the System Console/Standard Input Device | The asterisk (*) character can be used as the fileid specification for the system console/standard input (stdin) device. The system console is the:
For more information about the keyboard and standard input devices, see File Requirements. |
| z/OS fileid Usage Rules | If a DDNAME is specified, FastExport reads data records from the specified source. A DDNAME must obey the same construction rules as Teradata SQL column names, except that:
The DDNAME must obey the applicable rules of the external system and may reference a sequential or VSAM data set. If the DDNAME represents a data source on magnetic tape, the tape may be either labeled or unlabeled, as supported by the operating system. |
| Source File Record Restriction | A single record, row, or input line is accepted from the designated source. Always make sure that there is only one record in the file from which the ACCEPT command is getting the variables. |
| Coding Multiple Variables | When multiple variables are coded, each is sequentially assigned input text up to the first space character encountered that is not within a quoted string. |
| Delimiting Input Text | Input text for numeric values must be delimited only by space characters or record boundaries. Input text for character strings must be enclosed in apostrophes. For example, the data record provided to satisfy the following ACCEPT command should include two fields: .Accept age, name from file info; The following example shows two sample data records, where the first is correct but the second is not: 32 ’Tom’ 32 Tom |
| Number of Variables | When the number of variables listed is greater than the number of responses available, unused variables remain undefined (null). If there are not enough variables to hold all responses, FastExport issues a warning message. |