The Schedule RSF Transmission (SCDRSFTNS) command is used to schedule an RSF transmission to one or more remote locations.
The transmission can be scheduled to occur immediately, or at some future date and time. The transmission can consist of sending a package of objects, retrieving a package of objects, or performing any combination of RSF functions for each location to be contacted.
The prompted version of the SCDRSFTNS command is shown below. Click on the image to see parameter descriptions. Schedule RSF Transmission (SCDRSFTNS)
Type choices, press Enter.
Action to perform . . . *SND, *RTV, *PGM Server ID . . . Name, *LIST Schedule date . . . *CURRENT Date, *CURRENT Schedule time . . . *CURRENT Time, *CURRENT Automatic installation . . . *TRY *TRY, *YES, *NO Package . . . Name
User transmit program . . . Name
Library . . . *LIBL Name, *LIBL, *CURLIB Parameter string . . .
Library . . . *LIBL Name, *LIBL, *CURLIB Member name . . . *FIRST Name, *FIRST
Reset location list counts . . . *YES *YES, *NO Number of jobs to submit . . . . *DFT 1-255, *DFT
F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display F24=More keys
The parameters for the SCDRSFTNS command are described below in the order that they appear on the command prompt.
Action to perform
Indicate the action to perform for each location being contacted. This is a required parameter. The possible values are:
*SND: An RSF package is sent to each location. When you specify *SND for this parameter, you must
also specify a value for the "Package" parameter.
*RTV: An RSF package is retrieved from each location. When you specify *RTV for this parameter, you
must also specify a value for the "Package" parameter.
The save file retrieved will be placed in library QGPL and will have the same name as the server id from which it was retrieved. The SCDRSFTNS command does not delete the save file. You must delete the save file after installing the objects. You can manually delete the save file, or use an automatic
installation program that will delete the save file after installation. Click here for more information about automatic installation programs.
*PGM: A user written program is called to process each location. When you specify *PGM for this
parameter, you must also specify a value for the "User transmit program" parameter.
Server id
Enter a server id for the location to be contacted. This is a required parameter. The possible values are:
*LIST: No specific server id is referenced. Instead, a location list is used to contact several remote
locations. When you specify *LIST for this parameter, you must also specify a value for the "Location list" parameter. Click here for more information about location lists.
server-id: Enter a server id to reference from the server directory on your machine. Schedule date
Enter the date the transmission should begin. The possible values are:
date: Enter a valid future date on which to begin the transmission. Schedule time
Enter the time the transmission should begin. The possible values are:
*CURRENT: The transmission begins at the current time.
time: Enter a valid future time on which to begin the transmission. Automatic installation
Specify whether RSF should attempt to install a package once it has been sent or retrieved. This parameter is ignored if *PGM is specified for "Action to perform".
For automatic installation, RSF attempts to restore program RSFINST to library QTEMP from the save file that was transmitted with the package.
If program RSFINST can be restored, it is called with the following parameter list:
● A data structure describing the request, CHAR(*). See Appendix A for a complete description of the data
structure.
● Return message data. CHAR(128).
● Return message type. CHAR(7).
● Saved library. CHAR(10).
● Save command used. CHAR(10).
It is the user's responsibility to write installation program RSFINST and include it in the save file for the package if automatic installation for this package is to be supported. See Automatic Installation Programs for more information. The possible values are:
*TRY: Automatic installation is attempted. The request ends normally if no automatic installation
program is found. If you know automatic installation does not apply, it is more efficient to specify *NO for this parameter.
*YES: Automatic installation is attempted. The request ends in error if no automatic installation program
is found.
*NO: No attempt is made to automatically install the package. Package
Enter the name of an RSF package to reference for sending or retrieving objects. This parameter is required if a value other than *PGM is specified for the "Action to perform" parameter.
If *RTV is specified for "Action to perform", the package must exist on the remote machine. If *SND is specified for "Action to perform", the package must exist on the local machine.
The possible values are:
package-name: Enter the name of an RSF package. The save file associated with the package will be
sent to or retrieved from each remote location.
User transmit program
Enter the qualified name of a user program to call. This is a required parameter if *PGM is specified for the "Action to perform" parameter.
The program specified is called once for each remote location to be contacted. The program can send objects to, retrieve objects from, or perform any combination of valid RSF functions for the remote location.
The possible values are:
program name: Enter the name of a user-written program to call.
The possible library values are:
*LIBL: The library list is used to find the program. *CURLIB: The program is found in the current library.
library-name: Enter the name of the library containing the program.
The user program is passed the following parameters:
Server id: CHAR(10): The server id to be contacted.
Control data: CHAR(1024): A data structure containing control information about the location to be
contacted. All fields are in character format. The layout of the control data structure is as follows: 1-10: The name of the location list being used, if any.
11-20: The library containing the location list. 21-30: The member containing the location list. 31-40: The current status for the entry to be contacted. 41-50: The current step for the entry to be contacted. 51-53: The maximum number of tries for the entry. 54-56: The current try number.
57-1024: Reserved.
Location list
for the "Server id" parameter. Click here for more information about location lists. The possible values are:
location-list-name: Enter the name for the file containing the location list.
The possible library values are:
*LIBL: The library list is used to find the location list. *CURLIB: The location list is found in the current library
library-name: Enter the name of the library containing the location list. Member
Enter the name of the member containing the location list. The possible values are:
*FIRST: The location list stored in the first member of the file is used. member-name: Enter the name of the member containing the location list Reset location list
Specify whether to reset the access count and status for all entries in the location list. This parameter is ignored unless *LIST is specified for the "Server id" parameter.
The possible values are:
*YES: The location list is reset. Entries in the list are reset by the first job submitted by this command to
begin execution.
*NO: The location list is not reset. Number of jobs to submit
Specify the number of simultaneous jobs to submit to process the request. The possible values are:
*DFT: The value specified for the "Number of jobs to submit" parameter on the Create Location List
(CRTRSFLL) command for the location list being referenced is used. If no location list is referenced, 1 is assumed.
1-255: Specify the number of simultaneous jobs to submit to process the list. You should not submit
more jobs than lines available for use by RSF.
Job description
Specify the job descriptions to use when submitting jobs to process the request. The job descriptions determine the job queues to which jobs are submitted, and other job attributes.
You may specify up to 255 job descriptions. When multiple jobs are submitted to process the request, the first job uses the first job description, the second job uses the second job description, and so on. If more jobs are submitted than the number of job descriptions specified, the job description list is used repeatedly until all jobs have been submitted.
The possible single values are:
*DFT: The value specified for the "Job description" parameter on the Create Location List (CRTRSFLL)
command for the location list being referenced is used. If no location list is referenced, *USRPRF is assumed.
*USRPRF: The job description specified in the user profile of the user executing this command is used. job-description: Enter the name of an existing job description
The possible library values are:
*LIBL: The job description is found using the library list. *CURLIB: The job description is found in the current library.
library-name: Enter the name of the library containing the job description. Related Commands:
The following commands are discussed elsewhere in this manual:
Create Location List (CRTRSFLL)
Retrieve Location List Entry (RTVRSFLLE)
Change Location List Entry (CHGRSFLLE)
For more information about the following commands, prompt the command and press F1 to view the on-line help text:
Change Location List (CHGRSFLL)