When
you use bulk load in the
z/OS operating environment, the files that
the SQL*Loader uses must conform to
z/OS data set standards. The
data sets can be either sequential data sets or partitioned data sets.
Each filename that is supplied to the SQL*Loader are subject to extension
and FNA processing.
If you do not specify
filenames using data set options, default names in the form of
userid.SAS.
data-set-extension apply.
The
userid is the TSO prefix
when running under TSO, and it is the PROFILE PREFIX in batch. The
data-set-extensions are:
If you want to specify
filenames using data set options, you must use one of these forms:
For detailed information about these forms, see
the SQL*Loader chapter in the Oracle user's guide for
z/OS.
The Oracle engine runs
the SQL*Loader by issuing a host-system command from within your SAS
session. The data set where the SQLLDR executable file resides must
be available to your TSO session or allocated to your batch job. Check
with your system administrator if you do not know the name or availability
of the data set that contains the SQLLDR executable file.
On
z/OS, the bad file
and the discard file are, by default, not created in the same format
as the data file. This makes it difficult to load the contents of
these files after making corrections. See the section on SQL*Loader
file attributes in the SQL*Loader section in the Oracle user's guide
for
z/OS for information about overcoming this limitation.