z/OS Communications Server: IP User's Guide and Commands
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Receiving individual spool files

z/OS Communications Server: IP User's Guide and Commands
SC27-3662-00

Retrieving the spool files one at a time enables you to see whether a job ran correctly before you retrieve the rest of the output, giving you greater control over retrieving job information. If your FTP server is configured with JESINTERFACELEVEL=2, then a DIR command displays the output job completion code and the number and size of the job files. If JESINTERFACELEVEL=1, a DIR command displays the number of the output job files.

To retrieve the spool output while FILEtype=JES is specified, specify the job ID and either the number of the spool file or the JES data set name of the spool file that you want.

You can specify a short form of the job ID by entering the letter J followed by a 4-digit or 5-digit job number. For example:
GET JOB05444.1 JOB05444.FILE1 (REPLACE
GET JOB05766.6 ASSEMBLY.FILE6
GET JOB06235.2 (REPLACE
GET J6235.USER1.USER1.TSU00072.D0000002.JESMSGLG OUTPUT
GET JOB00275.4
GET J7438.3

In these examples, foreign_file is specified first, followed by local_file (on your client workstation) with the appropriate options, such as REPLACE. The first example requests that the first spool file for JOB05444 be transmitted and replace the file on your client named JOB05444.FILE1. The second command requests that the sixth spool file for JOB05766 be transmitted to your client with the name ASSEMBLY.FILE6. The fourth command has differing results depending on the JESGETBYDSN value that is configured. You can specify the JESGETBYDSN value as an option on the SITE subcommand or in the server FTP.DATA file, or accept the default value JESGETBYDSN FALSE.

If JESGETBYDSN FALSE is configured, the file named JOB06235.USER1.USER1.TSU00072.D0000002.JESMSGLG of job JOB06235 on the server host is submitted to JES. The resulting output is saved on the client in file OUTPUT. If the JESINTERFACELEVEL 2 statement is coded in the server FTP.DATA file and either the JESGETBYDSN option is specified on the SITE subcommand or JESGETBYDSN TRUE is coded in the server FTP.DATA file, the spool file with the JES data set name USER1.USER1.TSU00072.D0000002.JESMSGLG on the server host is stored on the client host in file OUTPUT. The JES spool file data set name has the same format as an MVS™ data set name and is case sensitive. You can find this data set using the SDSF utility on the Job Data Set (JDS) panel. Even though the JES spool file data set name has the same format as an MVS data set name, the name can be longer than an MVS data set name and can allow different character sets; it should not be enclosed in quotation marks. See z/OS SDSF Operation and Customization for more information about JES data set names. See Steps for submitting a job and automatically receiving output for more information about the behavior of the JESGETBYDSN parameter.

If you have specified FILEtype=JES, you can use the MGet subcommand to receive output from multiple jobs without specifying them one at a time. For example, you can enter:
MGET parameter
The FTP client requires an MGET subcommand parameter. The parameter is passed to the FTP server but is not used. The server returns all of the SYSOUT files for all the jobs in the HELD queue for your user ID for FTP servers configured for JESINTERFACELEVEL=1. For JESINTERFACELEVEL=2, all jobs that match the filters JESJOBNAME, JESOWNER and JESSTATUS are retrieved whether they are in the HELD queue or not. Note that the JESJOBNAME and JESOWNER SITE parameters allow wildcards (*,?). When using the MGET subcommand the JESOWNER value should be OUTPUT.
Notes:
  1. On an MVS FTP server, local_file must be specified.
  2. Truncation can cause a loss of data.
  3. A GET command performed on an empty data set erases the contents of the existing local data set.
  4. Receiving the output of a job does not remove the job output from the queue. To remove the job output from the queue, you must issue a DELETE command.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2013
This information center is Built on Eclipse™ ( www.eclipse.org ).