This chapter contains detailed descriptions of the commands and functions that pertain to RSF clients or requesters.
An iSeries machine that contacts other AS/400s, requesting to retrieve objects, send objects, initiate pass-through or call remote programs is an RSF requester. The machine receiving, processing, and fulfilling the requests is an RSF server. The requester is always the initiator of the transaction.
Since a single machine may be receiving and processing requests from remote sites, while at the same time sending its own requests to other sites, it follows that a given machine may be simultaneously acting as a requester and a server.
The Work With RSF Servers (WRKRSFSRV) command is used to work with a list of RSF servers, or to print a list of RSF servers. You make servers known to your machine by adding server directory entries.
The server directory on your machine functions like an on-line phone book. You can store phone numbers and other connection information in the server directory so you don't have to key it in with every request.
See Adding Server Directory Entries for more information about the details of server directory entries.
While working with servers, you can easily add, remove, change, copy, and rename server directory entries. You can also work with catalogs of RSF packages that are available from each server.
In addition, the Work With Servers display provides a convenient point from which you can initiate requests to remote machines to start pass-through, or transmit objects and files.
The prompted version of the WRKRSFSRV command is shown below.
The parameters for the WRKRSFSRV command are described below.
Indicate which entries to include in the list.
The possible values are:
*ALL: No entries are excluded based on name.
generic-name: Enter a generic name for the servers to be included in the list. Case is significant. An asterisk (*) in the generic specification will match any string of zero or more characters in the name. An underscore (_) in the generic specification will match any single character in the name.
Enter characters to compare to entry text to determine which entries should be included in the list. An entry is included in the list if the entry text contains the string specified. Case is not significant.
The possible values are:
*ALL: No entries are excluded based on text.
String: Enter any text string of up to 50 characters.
Indicates whether the list should be displayed or printed.
The possible values are:
*: Display the list.
*PRINT: Print the list.
Controls the amount of detail shown when printing the list.
The possible values are:
*BASIC: A subset of the total information is shown for each directory entry. Multiple entries are printed per page.
*FULL: All information is shown for each directory entry. One entry is printed per page.
The display that is presented when you specify OUTPUT(*) on the WRKRSFSRV command is shown below.
The following function keys may be used with this display:
F3: Exit without updating.
F5: Refresh the display.
F6: Add a new server directory entry.
F12: Cancel.
F13: Change user defaults.
F21: Present a system command line window.
The fields on the Work With RSF Servers display are explained below.
Enter a value in the "Position to" field and press Enter to position the list to a specific entry. The cursor is positioned to the first entry in the list that is greater than or equal to the "Position to" value you specify.
Enter an option number in the "Opt" column beside a list entry, and press Enter to perform a function on the list entry. You may enter options beside several list entries before pressing Enter. The options for the list entries are processed in turn when you press Enter. The following is a list of options and their functions.
2=Change: The CHGRSFSDE command prompt is displayed with the current values for the entry filled in.
3=Copy: A display is presented with which you specify the new names for entries to be copied.
4=Delete: A display is presented allowing you to confirm your choices for delete. When you press Enter a second time, the entries are deleted.
5=Display: Detailed information about the entry is displayed.
7=Rename: A display is presented with which you specify new names for the entries to be renamed.
12=Work with RSF catalog: The WRKRSFCAT display is presented for the selected server. The WRKRSFCAT display allows you to view a list of RSF packages available from the server and easily retrieve any package.
15=Start pass-through: A pass-through session is started with the server machine. The server must grant your machine permission to pass-through, by adding an entry to the requester directory on their machine. See Adding Requester Directory Entries for more information about adding and changing requester directory entries.
user-defined-option: You may key a user-defined option. To define new options, select option 9 from the Start PDM (STRPDM) menu.
See the on-line help text for this display for more information about user-defined options.
The unique server ID is shown in this column.
Text describing the server is shown. Type over the text and press Enter to change the text.
When you press F13, the Change User Defaults panel is presented. (Click here for more information.)
The following command is discussed elsewhere in this manual:
Add Server Directory Entry (ADDRSFSDE)
For more information about the following commands, prompt the command and press F1 to view the on-line help text:
Change Server Directory Entry (CHGRSFSDE)
Remove Server Directory Entry (RMVRSFSDE)
Rename Server Directory Entry (RNMRSFSDE)
The Add Server Directory Entry (ADDRSFSDE) command is used to add entries to the server directory on your machine.
The server directory functions like an on-line phone book. You can store phone numbers and other connection information in the server directory so that you won't have to key the information for every request.
The prompted version of the ADDRSFSDE command is shown below. Click on the image to jump to a particular command parameter description.
The parameters for the ADDRSFSDE command are described below in the order that they appear on the command prompt.
The name of the server directory entry to be added. This is a required parameter.
The possible values are:
name: Enter a valid system name for the new directory entry.
Specify the type of connection to use to communicate with the server machine.
The possible values are:
*SDLCDIAL: Use APPC over an SDLC dial-up connection. This is the easiest method to use for an SDLC dial-up network. RSF automatically creates the line, controller and device description at the beginning of the request and deletes them at the end of the request. Configuration objects are created according to the values specified in the RSF defaults for "Requester Configuration". See Setting Product Defaults for more information .
Note: The RSF server function (SDLC option) must be started on the server machine for this type of connection. (Click here for more information.)
*SDLC: Use APPC over a pre-configured connection. This option lets you use RSF over SDLC leased lines, Token Ring, Ethernet, X.25 and other connections that you have configured yourself.
*TCPDIAL: Use PPP and Sockets over a dial-up TCP/IP connection. This is the easiest method to use for a TCP/IP dial-up connection. RSF automatically creates the PPP profile as well as the line, controller and device descriptions at the beginning of the request and deletes them at the end of the request. Configuration objects are created according to the values specified in the RSF defaults for "PPP Requester Info". See Setting Product Defaults for more information .
Note: RSF release 7.0 or later must be installed on the server machine and the RSF server function (PPP and TCP/IP options) must be started on the server machine for this type of connection. (Click here for more information.)
*TCPIP: Use Sockets over a TCP/IP connection. This option allows you to connect to another AS/400 over any TCP/IP link, including the Internet.
Note: RSF release 6.0 or later must be installed on the server machine and the RSF server function (TCP/IP option) must be started on the server machine for this type of connection. (Click here for more information.)
The number to dial to reach the server's AS/400. This is a required parameter if either *SDLCDIAL or *TCPDIAL are specified for "Connection method".
The possible values are:
*NONE: No phone number is specified.
phone number: Enter up to 32 characters for the phone number. The number should include all digits necessary to make the phone connection, including a leading 1 plus area code, and a leading 9 for accessing an outside line where necessary.
A free-form description of the server directory entry.
The possible values are:
Characters: Enter up to 50 characters of information describing the server directory entry.
The phone number to pass to remote machines when requesting that they call your machine back. This call-back phone number will be used any time a request is initiated from your machine that references this server ID, and specifies CALBCKNBR(*SERVER) for the "Call-back phone number" parameter.
If the call-back request is accepted by the remote machine, the initial connection is dropped and your job waits for the remote machine to call back. Your job will wait up to 120 seconds plus the job default wait time for the server machine to call back before signaling an error.
This parameter is ignored unless *SDLCDIAL or *TCPDIAL is specified for "Connection method".
The possible values are:
*NONE: Call-back is not requested.
*RSFDFT: Callback is requested. The phone number specified in the RSF defaults for the line currently being used is passed to the server. See Setting Product Defaults for more information about viewing or changing the RSF defaults.
*MANUAL: Callback is requested, but the return call is placed manually by an operator at the remote site. Manual callback is useful if the remote server machine is attached to a phone line that is answered by a receptionist. When you specify *MANUAL for "Call-back phone number", RSF does not dial the server and request a call back. Instead, RSF immediately resets the line and gets ready for the server machine to call back. You must contact the remote location by voice and have an operator initiate the callback with the Call Back Using RSF (CALBCKRSF) command.
phone number: Callback is requested. Enter up to 32 characters for the callback phone number. The number should include all digits necessary to dial your machine from the server machine, including a leading 1 plus area code, and leading 9 for accessing an outside line where necessary.
If you imbed the special value &DFT anywhere in the phone number string, RSF will insert the default call-back number for the line currently being used at that point in the string. Only the first occurrence of &DFT in the string is replaced. Subsequent occurrences of &DFT are ignored. The special values &dft and &DFT are treated equivalently.
This parameter is used to associate the RSF server with a pre-configured line on your machine. When you specify a value other than *NONE for this parameter, the value specified for the "Server's RSF phone number" is ignored by RSF commands that initiate a request; an attempt is made to communicate with the server machine over a specific line that is already configured on your machine.
The communications line used must be compatible with APPC. The valid link types are SDLC, X.25, Token Ring, and Ethernet. See the Communications Users Guide for information about configuring communications lines on your machine. See "Using the Location Parameters" in the Advanced Program to Program Communications Programmer's Guide for more information about how the five elements of this parameter are used to select a communications device.
This is a required parameter if *SDLC is specified for "Connection method".
See Appendix C for step-by-step instructions for using your existing pre-configured lines with RSF.
*NONE: No pre-configured line is associated with this server.
location name: The name of a remote location associated with the server. The remote location name you specify is checked against the remote location name specified for device descriptions on your machine as the first step in selecting a communications device to use.
*LOC: Device names are ignored. The remote location name is used to select the device to use. This is the recommended value.
device name: The name of the device you want to use to communicate with the server machine. The device you name is selected if it is compatible with the remote location name, local location name and remote network id specified. Otherwise, the request will end in error.
*LOC: For non-APPN devices, any local location name will match. For APPN devices, *NETATR is used. This is the recommended value for this parameter.
*NETATR: The value specified for local location name in the network attributes of your machine is used.
location name: The name to use for your location. The local location name you specify is checked against the local location name specified for device descriptions on your machine as a step in selecting a communications device to use.
The name of a mode description to use for the communications session. The mode specified must be valid for the communications device selected on your machine and on the server machine.
The possible values are:
BLANK: The system supplied mode of BLANK is used. This is the recommended value.
*NETATR: The default mode specified in the network attributes of your machine is used.
Name: The name of a mode to use for the communications session.
*LOC: For non-APPN devices, any remote network id will match. For APPN devices, *NETATR is used. This is the recommended value for this parameter.
*NETATR: The value specified for local network id in the network attributes of your machine is used.
*NONE: For non-APPN devices, any remote network id will match. For APPN devices, *NETATR is used.
remote network id: The name of the remote network containing the server machine. The remote network id you specify is checked against the remote network id specified for device descriptions on your machine as a step in selecting a communications device to use.
Specify the name of an existing controller that RSF should vary on and off with each transaction.
This parameter is ignored unless *SDLC is specified for "Connection method".
The possible values are:
*NONE: No controller is varied on and off by RSF. If you are using a pre-configured connection, the line controller and device must be in a varied on state.
controller-name: The name of a controller to be varied on and off by RSF. The controller specified must exist and should be the controller to which the device specified in the CNNDEV parameter is attached. RSF will vary the controller off before the transaction, vary the controller on to begin the transaction, and vary the controller off at the completion of the transaction. RSF keeps track of active RSF connections using the controller and only varies the controller when it is not already in use by RSF.
Specify the name of an existing line that RSF should vary on and off with each transaction.
This parameter is ignored unless *SDLC is specified for "Connection method".
The possible values are:
*NONE: No line is varied on and off by RSF. If you are using a pre-configured connection, the line controller and device must be in a varied on state. If you specified *NONE for "Vary existing controller", you must also specify *NONE for this parameter.
line-name: The name of a line to be varied on and off by RSF. The line specified must exist and should be the line to which the device specified in the CNNDEV parameter is attached. RSF will vary the line off before the transaction, vary the line on to begin the transaction, and vary the line off at the completion of the transaction. RSF keeps track of active RSF connections using the line and only varies the line when it is not already in use by RSF.
Specify a requester line group to use when contacting this server.
See Requester Configuration for more information about assigning requester lines to groups.
This parameter is ignored unless *SDLCDIAL or *TCPDIAL is specified for "Connection method".
The possible values are:
*ANY: Any requester line can be used to contact this server.
*BLANK: Only requester lines that are not assigned to a specific group can be used to contact this server.
group-name: The name of the requester line group to use. Only lines in the specified group are used to contact this server.
Specify the network name or IP address of the remote system to connect to. If a name is specified, it must map to a valid IP address (Internet address) using the TCP/IP host table on this machine, or using a name server.
This parameter is required if *TCPIP or *TCPDIAL is specified for "Connection method".
The possible values are:
*INTNETADR: This value is provided for compatibility with earlier releases. An address is specified, using the Internet Address (INTNETADR) parameter instead of specifying a system name or IP address here. When *INTNETADR is specified for this parameter, you must specify a value for the INTNETADR parameter.
Name: Enter the fully qualified name of the remote system.
IP-address: Specify the Internet address of the remote machine in the form nnn.nnn.nnn.nnn, where nnn is a number from 0 to 255.
Enter the address of the remote machine.
This parameter is ignored unless *INTNETADR is specified for the "Remote system" parameter.
The possible values are:
Address: Specify the Internet address of the remote machine. The address should be specified in the form nnn.nnn.nnn.nnn, where nnn is a decimal number from 0 to 255.
Specify the TCP/IP port to connect to on the remote machine for RSF functions. The value specified for this parameter must match the value specified for the PORT parameter on the Start Server Function (STRRSFSRV) command on the server machine. (Click here for more information.)
This parameter is ignored unless *TCPIP or *TCPDIAL is specified for "Connection method".
The possible values are:
602: A default port of 602 is used.
Port-number: Specify a valid port number from 1 to 65534.
Specify the TCP/IP port to use when connecting with telnet to the remote machine. The Start Pass-Through Using RSF (STRPASRSF) command uses telnet under the covers for TCP/IP connections.
This parameter is ignored unless *TCPIP or *TCPDIAL is specified for "Connection method".
The possible values are:
23: A default port of 23 is used.
Port-number: Specify a valid port number from 1 to 65534.
Specify the TCP/IP port to use for broadcasting to the remote machines. Only machines listening on this port will receive the broadcast. (The value specified for this parameter must match the value specified for the BPORT parameter on the Start Server Function (STRRSFSRV) command on the server machine.)
This parameter is ignored unless *BROADCAST is specified for "Connection Method".
The possible values are:
603: A default port of 603 is used.
Port-number: Specify a valid port number from 1 to 65534.
Specify the broadcast group IP address. Only machines monitoring the specified IP address on the specified port will receive the broadcast. (The value specified for this parameter must match the value specified for the GRPADR parameter on the Start Server Function (STRRSFSRV) command on the server machine.)
This parameter is ignored unless *BROADCAST is specified for "Connection Method".
A valid multicast group address must be in the range of 224.0.0.0 to 232.255.255.255. Addresses from 224.0.0.0 to 224.0.0.255 are intended for intra-network transmissions. Therefore, transmissions to these addresses are typically not forwarded by multicast-capable routers. See RFC1700 for a list a list of reserved multicast group addresses.
The possible values are:
group-address: Specify the broadcast group IP address in the form nnn.nnn.nnn.nnn, where nnn is a number from 0 to 255.
Specify the IP address of the interface on this machine that will be used to send broadcast transmissions. You can use option 1 on the NETSTAT display to list the available interfaces.
This parameter is ignored unless *BROADCAST is specified for "Connection Method".
The possible values are:
interface-address: Specify the broadcast interface IP address in the form nnn.nnn.nnn.nnn, where nnn is a number from 0 to 255.
Specify the number of bytes to broadcast before pausing to let the receiving machines catch up.
Depending on your network, broadcast messages may arrive at one or more target machines more quickly than they can be processed. If the receive buffer gets full on the target machine, additional messages my be discarded by the system, invalidating the transmission for that system.
Setting the appropriate block size and inter-block delay can help ensure that the complete transmission gets through to the maximum number of target systems, while not excessively impacting performance.
A smaller block size and/or longer inter-block delay increases transmission integrity. A larger block size and/or smaller inter-block delay improves performance.
This parameter is ignored unless *BROADCAST is specified for "Connection Method".
The possible values are:
63500: A default block size of 63500 bytes is used.
number: Enter a integer, greater than zero.
Specify the number of hundredths of a second to pause after sending each block of broadcast data. This parameter works in conjunction with the Broadcast Block Size (BBLOCK) parameter to ensure that the complete transmission gets through to the maximum number of target systems, while not excessively impacting performance.
A smaller block size and/or longer inter-block delay increases transmission integrity. A larger block size and/or smaller inter-block delay improves performance.
This parameter is ignored unless *BROADCAST is specified for "Connection Method".
The possible values are:
50: A default of 50 (half a second) is used.
number: Enter a number from zero to 100.
Specify the maximum number of gateways that a broadcast message may pass through before the message is discarded. This helps prevent looping.
This number should be at least as large as the number of gateways between the sending and receiving machines.
This parameter is ignored unless *BROADCAST is specified for "Connection Method".
The possible values are:
10: A default of 10 is used.
number: Enter a number from 1 to 255.
Specify the type of encryption to use for TCP/IP connections. When a value other than *NONE is specified, all information passed between the client and server is encrypted, including control information, user profiles, passwords and data.
This parameter is ignored unless *TCPIP or *TCPDIAL is specified for "Connection method".
The possible values are:
*BASIC: Basic symmetric encryption is used. When this option is used, the encryption key specified using the "Encryption Key Data Area" parameter must match the encryption key that was specified on the server machine using the Change RSF Defaults (CHGRSFDFT) command. See Setting Product Defaults for more information about changing defaults.
This option provides enough security for private networks and for those Internet transmissions where maximum secrecy and confidentiality are not required.
*NONE: The transmission is not encrypted. This option provides slightly better transmission performance.
*SSL: The Secure Sockets Layer protocol is used to encrypt the transmission. This option provides maximum security, allowing for the safe transmission of the most confidential information.
Note:: In order to use this option:
1. The Internet Connection Secure Server licensed program must be installed on
your machine and the server machine. (US version: 5769NC1. International
version: 5769NCE.) Contact your IBM sales representative for more information.
2. RSF's SSL support must be enabled on your machine and the server machine.
This is done with the Change Defaults (CHGRSFDFT) command. See
Setting Product Defaults for more information. See Appendix G for
information about configuring SSL,
Enter the qualified name of a data area containing the encryption key to use. The data area must be at least 128 bytes long.
This parameter is ignored unless *TCPIP or *TCPDIAL is specified for the "Connection Method" parameter, and *BASIC is specified for the "Encryption" parameter.
The first 128 bytes of the data area are used as the encryption key. Trailing blanks in the key are ignored. The key can be from 1 to 128 bytes long and may contain any valid hex or character data. Longer keys provided greater security.
The data area does not need to exist at the time this command is run but it must exist when a transmission is started.
The possible values are:
*NONE: No data area is used. A default key is supplied by RSF.
data-area name: The name of a data area to use
The possible library values are:
*LIBL: The job library list is used to locate the data area.
library-name: The name of the library containing the data area.
Indicate whether to compress data as it is transmitted to this location.
The goal of compression is to get data from point A to point B more quickly. Since compression uses more CPU resources, run-time compression is most effective over slower connections, where the transmission speed is significantly slower than the processor speed.
When compression is selected, an informational message is sent to the job log at the completion of the transmission indicating the amount of compression achieved.
Note: This parameter only effects TCP/IP connections. Use the Change Mode Description (CHGMODD) command for mode BLANK to set run-time compression options for SDLC connections.
The possible values are:
*NONE: The data is not compressed.
*BASIC: A simple TERSE algorithm is used to compress data as it is transmitted. This requires more CPU than *NONE, but less CPU than the *MAX option.
*MAX: The LZ1 algorithm is used to compress data as it is transmitted. This requires more CPU than the *NONE or *BASIC options, but the best compression ratio is achieved.
For dial-up TCP/IP connections (PPP), indicate the protocol to use when sending user ID and password information to the remote machine.
This parameter is ignored if a value other than *TCPDIAL is specified for "Connection Method", or if *DFT is specified for the "Remote Signon" parameter.
The possible values are:
*CHAP: The user ID and password are encrypted before they are sent. You should specify this value whenever the remote machine is an iSeries or AS/400 running RSF, or whenever the server supports the CHAP protocol.
*PAP: The user ID and password are sent as plain text. Many Internet service providers only support this option. Check with your ISP to determine which password protocols are supported.
For dial-up TCP/IP connections (PPP), indicate if RSF should define a default route or specific static routes to the remote location for the duration of the connection.
Routes are useful if you want to use the remote machine as a gateway to connect to other machines. See option 2 on the CFGTCP menu for more information about TCP/IP routes.
This parameter is ignored if a value other than *TCPDIAL is specified for Connection Method.
The possible network address values are:
*NONE: No static routes to the remote system are defined.
*DFT: A default route to the remote system is defined for the duration of the connection. When the iSeries is asked to connect to any unknown IP address, it will try to find a route to that address beginning with the connection designated as the default route.
Note: The iSeries allows only one default route to be active at a time. When you specify *DFT for this parameter, a connection to the remote system will fail if:
Another default route is defined in your TCP/IP configuration.
A connection to a different RSF server is already active which has *DFT specified for Static Routes.
*IP-address: Enter the address of the remote network to which you wish to establish a route. The address should be formatted as a valid IP network address. Network addresses end in 0 for a subnet mask of 255.255.255.0. Network addresses end in 0 or 128 for a subnet mask of 255.255.255.128.
The possible Subnet Mask values are:
255.255.255.0: This common subnet mask is the default.
mask: Enter a valid subnet mask.
Specify the qualified name of a data area to use to send default messages to this server. The data area must be at least 128 bytes long
If a data area is specified for this parameter, and if the user specifies *SERVER for the "Message for server" (MSG) parameter on one of the RSF commands that initiates a request, the first 128 bytes of the data area are sent to the server as message data.
Message data sent via the MSG parameter is accessible by pre- and post-processing programs on the server machine. Associating a message data area with a server directory entry allows the server location to receive customized information with every request.
For example: A data area could be created on the requester machine to track different software features and releases installed. Then, by tying the data area to the server location using this parameter, the server receives the feature and release information with every request.
The possible values are:
*NONE: No data area is associated with this server. If *SERVER is specified for the "Message for server" parameter on an RSF command that initiates a request and the command references this server, no message is sent.
data-area name: The name of a data area to use. The data area must be at least 128 bytes long.
The possible library values are:
*LIBL: The job library list is used to locate the data area.
library-name: The name of the library containing the data area.
Indicate whether this machine should relay transmissions to this server when the server is in the list of machines to receive the distribution.
For a relay distribution, machines that successfully receive a transmission participate in sending the transmission on to other locations in a list that is specified by the original sender.
Note: More than one machine can be set to forward distributions to a given server. This ensures that there are multiple paths to that server. If one machine is unable to contact the server, another may be able to get through. RSF ensures that only one copy of the distribution is ultimately sent to the server.
This parameter is ignored for non-relay distributions.
The possible values are:
*YES: During a relay distribution, this machine will attempt to send the transmission this server.
*NO: This server will not be contacted by this machine for a relay distribution. Some other machine must relay to this server.
Fallback support allows you to specify alternate connection information for a given server. If a connection cannot be made using the connection information specified in this server ID, RSF will attempt to connect using the connection information specified in the fallback server ID, if one is specified.
The fallback server may have its own fallback server ID specified. In this way, you can chain together as many server IDs as you like. Care should be taken to ensure that the chain of fallback servers is not recursive--no entry should point an earlier entry in the chain.
The different server IDs that make up the fallback chain may have completely different connection methods defined. Or, one entry may be simply a variation of an earlier entry in the chain, with a different connection phone number or IP address, for example.
The possible values are:
*NONE: No fallback server ID is defined for this server.
server-ID: Enter the name of an existing server ID to use as a fallback. If a connection cannot be made to this server directly, an attempt will be made to connect using the fallback server ID.
Specify the preferred time for contacting this location. This information may be used by other RSF functions to schedule transmissions.
The possible single values are:
*ANY: The location can be contacted any time. This is the same as entering 00:00:00 to 23:59:59 for the time range.
The other possible values are:
time-range: Enter start and end times for the optimal transmit window, using a 24-hour clock. If a start time is not specified, 00:00:00 is assumed. If an end time is not specified, 23:59:59 is assumed. If the end time is less than the start time, the window spans midnight.
Specify the user profile and password to use when connecting to the remote machine.
For SDLC connections (Connection Method *SDLCDIAL or *SDLC), this parameter determines the user ID and password to use to sign on to the remote machine. The RSF job on the target machine runs under the specified user ID.
For TCP/IP dial-up connections (Connection Method *TCPDIAL), this parameter determines the user ID and password to pass to the target PPP profile. The actual user profile under which the target job runs, however, is determined by job description RSF/RSFTCP.
The possible single values are:
*DFT: For SDLC connections, RSFSRV is used for the profile and password.
This is the recommended value for SDLC connections as it will allow you to connect to most machines with RSF. However, if the password
for the RSFSRV profile on the target machine was changed from the default value, the connection will fail with message RSF4041 or
RSF4011. See
Security Considerations for more information about using the default profile and password.
For PPP connections (Connection Method *TCPDIAL), a value of *DFT for this parameter passes no user ID or password to the remote
machine at connection time.
The other possible values are:
profile-and-password: Specify a user profile and password to use to initiate the RSF
server job on the target machine.
For SDLC connections, both values must be ten or fewer characters, without embedded
blanks. Case is not significant. The profile/password combination must be valid for the remote machine,
otherwise the connection will fail with message RSF4041 or RSF4011.
For PPP/TCPIP connections, the user ID and password may each be up to thirty characters long and may include
imbedded blanks. Case is significant. The user ID/password combination must match an entry
in the validation list specified in the server configuration on the target machine.
The following command is discussed elsewhere in this manual:
Work With Servers (WRKRSFSRV)
For more information about the following commands, prompt the command and press F1 to view the on-line help text:
Change Server Directory Entry (CHGRSFSDE)
Remove Server Directory Entry (RMVRSFSDE)
Rename Server Directory Entry (RNMRSFSDE)
The Work With RSF Catalog (WRKRSFCAT) command is used to work with a list of RSF packages available from a given server, or to print a list of packages available from a given server.
While working with an RSF catalog, you can easily display and delete catalog entries, retrieve packages, and retrieve catalog updates.
The prompted version of the WRKRSFCAT command is shown below.
The parameters for the WRKRSFCAT command are described below.
The name of the server whose catalog is to be worked with. This is a required parameter.
The possible values are:
Name: Enter the name of an existing server directory entry.
Indicates whether the list should be displayed or printed.
The possible values are:
*: Display the list.
*PRINT: Print the list.
Controls the amount of detail shown when printing the list.
The possible values are:
*BASIC: A subset of the total information is shown for each catalog entry. Multiple entries are printed per page.
*FULL: All information is shown for each catalog entry. One entry is printed per page.
The display that is presented when you specify OUTPUT(*) on the WRKRSFCAT command is shown below.
The following function keys may be used with this display:
F3: Exit without updating.
F4: Prompt.
F5: Refresh the display.
F12: Cancel.
F13: Change defaults that effect this display.
F15: Retrieve the latest catalog.
F21: Present a system command line window.
The fields on the Work With RSF Catalog display are explained below.
The name and text for the server whose catalog is being worked with are shown.
Enter a value in the "Position to" field and press Enter to position the list to a specific entry. The cursor is positioned to the first entry in the list that is greater than or equal to the "Position to" value you specify.
Enter an option number in the "Opt" column beside a list entry, and press Enter to perform a function on the list entry. You may enter options beside several list entries before pressing Enter. The options for the list entries are processed in turn when you press Enter. The following is a list of options and their functions.
4=Delete: A display is presented allowing you to confirm your choices for delete. When you press Enter a second time, the entries are deleted.
5=Display: Detailed information about the entry is displayed.
8=Retrieve package: Retrieve the package from the server. Press Enter to retrieve the package. Press F4 to be prompted for parameters before retrieving the package. The package is retrieved interactively or in batch, depending on the values specified for defaults. Press F13 to view or change the defaults.
10=Install: The selected package is installed on your system. The package status must be RTV or OPN.
The names of the packages available from the server are shown in this column.
The package status is shown. The possible values are:
blank: The package has not been retrieved or installed.
RTV: The package has been retrieved but not installed.
INL: The package has been installed.
OPN: The package has been retrieved again after it was installed.
Text describing each package is shown in this column.
Press F15 to retrieve the latest catalog from the server. The catalog is retrieved interactively or in batch, depending on the values specified for defaults. Press F13 to view or change the defaults.
The display that is presented when you press F13 to change defaults from the WRKRSFCAT display is shown below. You can also access this display by running the Change User Options (CHGRSFUO) command from any command line. Click on the image to see parameter descriptions.
The following function keys may be used with this display:
F3: Exit without updating.
F12: Cancel.
The fields on the Change Defaults display are explained below.
The qualified name of a save file on your machine where retrieved packages should be placed. If the save file specified does not exist when the package is retrieved, it will be created.
The possible values are:
*PKG: Use the name of the package being retrieved for the save file name.
name: Enter the name of the save file to contain retrieved packages.
The possible library values are:
QGPL: Library QGPL is used.
*CURLIB: Your current library is used.
library name: Enter the name of a library to contain the save file.
Specify the action to take when the specified save file already exists.
The possible values are:
*YES: Replace an existing save file.
*NO: End in error if the specified save file already exists.
Specify whether to automatically install retrieved packages.
The possible values are:
*YES: RSF runs program RSFINST if it is included within a retrieved package.
*NO: Package save files are not automatically installed.
Specify whether to retrieve packages that are already flagged as installed on your system.
The possible values are:
*NO: A request to retrieve an installed package ends in error.
*YES: Installed packages may be retrieved again.
Specify whether to submit requests to batch.
The possible values are:
*NO: Run requests interactively.
*YES: Submit requests to batch.
Enter the qualified name of a job description to use when submitting requests to batch.
The possible values are:
name: Enter the name of the job description to use.
The possible library values are:
*LIBL: The job description is found using the library list.
*CURLIB: The job description in the current library is used.
library-name: Enter the name of the library containing the job description.
Enter the earliest date to include in the catalog list. Only catalog entries that were created or changed on or after the date specified are included.
The possible values are:
*FIRST: No minimum date is used to filter catalog entries.
*NEW: Only new entries that were added to the catalog since the last time the catalog was retrieved are included.
date: Enter the earliest date to include in the list.
Enter the latest date to include in the catalog list. Only catalog entries that were created or changed on or before the date specified are included.
The possible values are:
*LAST: No maximum date is used to filter catalog entries.
date: Enter the latest date to include in the list.
Use this parameter to select entries to include by status.
The possible single values are:
*ALL: All entries are included regardless of status.
*NOTBLANK: Entries with any status other than blank are included.
*NOTINL: Entries for packages that have not been installed are included.
The other possible values are:
*BLANK: Entries for packages that have not been retrieved or installed are included.
*RTV: Entries for packages that have been retrieved but not installed are included.
*INL: Entries for packages that have been installed are included.
*OPN: Entries for packages that have been retrieved again after they were last installed are included.
Enter characters to compare to catalog entry text to determine which entries should be included in the list. An entry is included in the list if the entry text contains the string specified.
The possible values are:
*ALL: Include all entries regardless of their text.
string: Enter a text compare string to use.
Enter the qualified name of a user option file to use when checking user-defined options.
The possible values are:
file-name: Enter the name of an existing option file.
The possible library values are:
*CURLIB: The file is found in the job's current library.:
*LIBL: The file is found using the library list.:
library-name: Enter the name of the library containing the option file.:
Enter the name of the option file member to use.
The possible values are:
*FIRST: The first member in the file is used.
member-name: Enter a valid member name.
Specify a default server ID to use to replace the &SERVER variable in user-defined options. This value is only used with the Work With Packages display.
The possible values are:
*NONE: No default is specified.
server-ID: Enter a valid server ID.
Specify a default package to use to replace the &PKG variable in user-defined options. This value is only used with the Work With Servers and Work With Catalog displays.
The possible values are:
*NONE: No default is specified.
package-name: Enter a valid package name.
The following commands are discussed elsewhere in this manual:
Retrieve Package (RTVRSFPKG)
Send Package (SNDRSFPKG)
Create Package (CRTRSFPKG)
For more information about the following commands, prompt the command and press F1 to view the on-line help text:
Change Package (CHGRSFPKG)
Delete Package (DLTRSFPKG)
Rename Package (RNMRSFPKG)
The Retrieve RSF Package (RTVRSFPKG) command is used to retrieve a package of objects from another machine.
With this command, you can only retrieve objects that have been included in an RSF package on the remote machine. Use the commands in RSFTOOLS (Appendix B) to retrieve objects that have not been defined by an RSF package. Use the Copy File Using RSF (CPYFRSF) command to send and retrieve database file members that are not part of a package. You can also use the Retrieve IFS Objects (SNDIFSRSF) to retrieve objects that are not part of a package.
If a set of objects will be retrieved from a given machine multiple times, it is most efficient to define a package for the objects and retrieve them using this command. Click here for more information about creating packages of objects.
The prompted version of the RTVRSFPKG command is shown below. Click on the image to see parameter descriptions.
The parameters for the RTVRSFPKG command are described below.
The name of the package you want to retrieve from the server machine. The package must exist on the server machine. This is a required parameter.
The possible values are:
name: The name of a specific package to access from the server.
*CATALOG: A special request is sent to the server to download a catalog of RSF packages available on their machine. When *CATALOG is specified for "Package", you cannot specify *NONE for "Server id".
*NONE: No package is retrieved. An ad hoc message is sent to the server. When *NONE is specified for "package", you cannot specify *NONE for "Message for server".
The qualified name of a save file on your machine to receive the RSF package. This is a required parameter.
The possible values are:
name: The name of a save file to contain the received package. If the file does not exist, it will be created. A save file name must be provided unless *CATALOG is specified for "Package" or a value other than *ALL or *DATA is specified for "Type of data requested".
*NONE: No target save file is used. *NONE must be specified when *CATALOG is specified for "Package", or when a value other than *ALL or *DATA is specified for "Type of data requested".
The possible library values are:
*CURLIB: The current library is used to locate the save file.
library name: The name of an existing library which contains or will contain the save file.
Specify whether RSF should replace the contents of the save file if it already exists.
The possible values are:
*NO: If the save file already exists, the request ends in error.
*YES: The contents of the save file are replaced with the data being downloaded. When *RETRY is specified for "Type of data requested", the new data is appended to the existing save file.
The name of a server directory entry to be referenced. The entry must exist in the server directory on your machine. See Adding Server Directory Entries for more information.
The possible values are:
*CURRENT: Reference the server that is currently associated with the job. For pass-through target jobs, *CURRENT refers to the source machine. For an RSF pre-processing program running on a server machine, *CURRENT refers to the requester machine. *CURRENT is only valid for this parameter if the job executing the command is an RSF target pass-through job, an RSF pre-processing program executing on the server machine, or a batch job submitted from one of the above two job types. See Starting Pass-Through for more information about RSF pass-through jobs. See Pre-processing Programs for more information about pre-processing programs.
name: The name of an entry in the server directory on your machine.
The type of data you wish to download
The possible values are:
*ALL: All data associated with the RSF package is downloaded to your machine.
*CVRLTR: Only the cover letter is retrieved.
*DATA: Only the save file data is retrieved.
*MSG: No data is retrieved. A message is sent to the server machine. When you specify *MSG for "Type of data requested", you cannot specify *NONE for "Message for server".
*RETRY: Specify *RETRY to resume the download for a package that was previously interrupted. When you specify *RETRY, Remote Software Facility determines where the previous download attempt left off, and resumes the transmission at that point. Cover letter data is not retrieved. Only the save file data for the package is retrieved. You must specify the same save file for "Target save file" that was used in the previously interrupted transaction.
Specify whether RSF should hang up the phone connection at the completion of the transaction. This parameter is ignored for non-switched connections.
The possible values are:
*YES: The line is disconnected at the completion of the transaction.
*NO: The server is notified that you would like the line to remain active at the completion of the transaction. The line will remain active if the server has specified HANGUP(*NO) for a requester directory entry on the server machine that refers to your machine. Otherwise, the server hangs up at the end of the transaction. See Adding Requester Directory Entries for more information.
When HANGUP(*NO) is specified by both the requester and server machines, the line remains active until one of the following occurs:
Another request from your machine to the same server
specifies HANGUP(*YES)
The requester explicitly hangs up using the ENDRSFCNN
(End RSF Switched Connection) command. See Hang up: End
RSF Switched Connection for more information.
The time limit expires on the server machine and the server hangs up. The time limit is set with the SRVDSC parameter on the Change RSF Defaults (CHGRSFDFT) command. See Setting Product Defaults for more information about changing RSF defaults.
Specify whether RSF should attempt to install a package once it has been retrieved.
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 server'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.
The phone number to pass to the server machine when requesting that the server call your machine back.
Your call-back request will be rejected by the server unless a requester directory entry exists on the server machine which refers to your machine, and specifies *YES for "Allow call-back". See Adding Requester Directory Entries for more information.
If the call-back request is accepted by the server, the initial connection is dropped and your job waits for the server machine to call back. Your job will wait for about two minutes for the server machine to call back before signaling an error.
The possible values are:
*NONE: Call-back is not requested.
*RSFDFT: Call-back is requested. The phone number specified in the RSF defaults for the line currently being used is passed to the server. See Setting Product Defaults for more information about viewing or changing the RSF defaults.
*SERVER: Call-back is requested. The call-back phone number specified in the server directory entry named in the "Server id" parameter is used. If no call-back phone number is specified in the server directory entry, a value of *NONE is assumed for this parameter.
*MANUAL: Call-back is requested, but the return call is placed manually by an operator at the remote site. Manual call-back is useful if the remote server machine is attached to a phone line that is answered by a receptionist. When you specify *MANUAL for "Call-back phone number", RSF does not dial the server and request a call back. Instead, RSF immediately resets the line and gets ready for the server machine to call back. You must contact the remote location by voice and have an operator initiate the call-back with the Call Back Using RSF (CALBCKRSF) command.
phone number: Call-back is requested. Enter
up to 32 characters for the call-back phone number. The number should include
all digits necessary to dial your machine from the server machine, including a
leading 1 plus area code, and a leading 9 for accessing an outside line where
necessary.
If you imbed the special value &DFT anywhere in the phone number string,
RSF will insert the default call-back number for the line currently being used
at that point in the string. Only the first occurrence of &DFT in the
string is replaced. Subsequent occurrences of &DFT are ignored. The special
values &dft and &DFT are treated equivalently.
Indicate whether to compress data as it is transmitted.
The goal of compression is to get data from point A to point B more quickly. Since compression uses more CPU resources, run-time compression is most effective over slower connections, where the transmission speed is significantly slower than the processor speed.
When compression is selected, an informational message is sent to the job log at the completion of the transmission indicating the amount of compression achieved.
Note: This parameter only effects TCP/IP connections. Use the Change Mode Description (CHGMODD) command for mode BLANK to set run-time compression options for SDLC connections.
The possible values are:
*SERVER: The compression option specified in the server directory entry named in the "Server id" (SERVER) parameter is used. See Adding Server Directory Entries for more information.
*NONE: The data is not compressed.
*BASIC: A simple TERSE algorithm is used to compress data as it is transmitted. This requires more CPU than *NONE, but less CPU than the *MAX option.
*MAX: The LZ1 algorithm is used to compress data as it is transmitted. This requires more CPU than the *NONE or *BASIC options, but the best compression ratio is achieved.
Specify whether to retrieve the package if it is flagged as installed on your system.
The possible values are:
*NO: The request to retrieve an installed package ends in error.
*YES: An installed package may be retrieved again.
An ad hoc message to be sent to the server along with the RSF request.
The possible values are:
*NONE: No message is sent to the server.
*SERVER: Get the message data from the data area specified in the server directory entry named in the "Server id" parameter. If no message data area is specified in the server directory entry, a value of *NONE is assumed for this parameter.
Message text: Enter up to 128 characters of message text.
When you prompt for command parameters with F4, default name, address and telephone information are filled in for you. These are the same defaults the system uses to send PTF orders via Electronic Customer Support.
The possible values are:
contact information: Enter the appropriate information for contact name, address, and phone.
The following commands are discussed elsewhere in this manual:
Send Package (SNDRSFPKG)
Work With Catalog (WRKRSFCAT)
Copy File Using RSF (CPYFRSF)
Retrieve Objects (RTVOBJRSF)
Send Objects (SNDOBJRSF)
Retrieve Documents (RTVDOCRSF)
Send Documents (SNDDOCRSF)
Create Package (CRTRSFPKG)
For more information about the following commands, prompt the command and press F1 to view the on-line help text:
Change Package (CHGRSFPKG)
Delete Package (DLTRSFPKG)
Rename Package (RNMRSFPKG)
The Send RSF Package (SNDRSFPKG) command is used to send an RSF package to a remote server.
With this command, you can only send objects that have been included in an RSF package on your machine. Use the commands in RSFTOOLS (Appendix B) to send objects that have not been defined by an RSF package. Use the Copy File Using RSF (CPYFRSF) command to send and retrieve database file members that are not part of a package. You can also use the Send IFS Objects (SNDIFSRSF) to send objects that are not part of a package.
If a set of objects will be sent from a given machine multiple times, it is most efficient to define a package for the objects and send them using this command. Click here for more information about creating packages of objects.
The prompted version of the SNDRSFPKG command is shown below. Click on the image to see parameter descriptions.
The parameters for the SNDRSFPKG command are described below.
The name of the package you want to send. The package must exist on your machine. See Creating Packages for more information about creating RSF packages. This is a required parameter.
The possible values are:
name: The name of a specific package to send.
*NONE: No package is sent. An ad hoc message is sent to the server. When *NONE is specified for "Package", you cannot specify *NONE for "Message for server".
*SAVF: No predefined package definition is used. In stead, you use the "Save file" parameter to indicate the save file to send.
The name of a server directory entry to be referenced. The entry must exist in the server directory on your machine. See Adding Server Directory Entries for more information.
The possible values are:
*CURRENT: Reference the server that is currently associated with the job. For pass-through target jobs, *CURRENT refers to the source machine. For an RSF pre-processing program running on a server machine, *CURRENT refers to the requester machine. *CURRENT is only valid for this parameter if the job executing the command is an RSF target pass-through job, an RSF pre-processing program executing on the server machine, or a batch job submitted from one of the above two job types. See Starting Pass-Through for more information about RSF pass-through jobs. See Pre-processing Programs for more information about pre-processing programs.
Notes:
*CURRENT is not valid for Server ID for RSF
commands run in a target Telnet session. *CURRENT is allowed within other RSF
server jobs that connect via TCP/IP.
For SNA/APPC connections, the user profile and password used to connect back to the *CURRENT machine are taken from the server entry that is associated with the job in which this command is run. If no server entry is associated with the job, the default RSF signon is used. Use the WRKRSFRQS command to view or change the server IDs that are associated with requests sent to this machine.
*LIST: All locations in a list of servers are contacted. When you specify *LIST for this parameter, you must also specify a value for the Location List (LIST) parameter.
RSF begins contacting the locations in the list a soon as this command is run. Use the Schedule RSF Transmission (SCDRSFTNS) command if you want to schedule the transmission for a later time.
name: Enter the name of an entry in the server directory on your machine.
The type of data you wish to send to the server machine.
The possible values are:
*ALL: All data associated with the package is sent to the server machine.
*CVRLTR: Only the cover letter is sent.
*DATA: Only the save file data is sent.
*MSG: No data is sent. A message is sent to the server machine. When you specify *MSG for "Type of data to send", you cannot specify *NONE for "Message for server".
*RETRY: Specify *RETRY to resume sending a package that was previously interrupted. When you specify *RETRY, Remote Software Facility determines where the previous transmission left off, and resumes the transmission at that point. Cover letter data is not sent. Only the save file data for the package is sent.
Specify the name of a program to call on the remote machine once the package has arrived.
The value you specify will be ignored by the server machine unless an entry referring to your machine exists in the requester directory of the server machine and specifies *YES or *PARTIAL for "Allow remote program calls". See Adding Requester Directory Entries for more information about requester directory entries.
The possible values are:
*DFT: The value specified for "Post-Processing program" in the requester directory of the server machine is used. The server machine controls which program, if any, is called.
*INSTALL: Automatic installation program RSFINST is called. 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.
*NONE: No program is called on the server machine once the data arrives.
Name: Enter the qualified name of a program to call on the server machine. See Post-Processing Programs for more information about how to write these programs.
The possible library values are:
*LIBL: The job library list is used to locate the program.
library name: The name of the library on the server machine containing the program to be called.
Specify whether to invoke the pre-processing program associated with the package. This parameter is ignored if no pre-processing program is associated with the package. See Pre-Processing Programs for more information.
The possible values are:
*YES: Invoke the pre-processing program associated with the package, if one exists, before sending the package to the server.
*NO: Ignore any pre-processing program associated with the package.
Specify whether access information for the RSF package should be updated upon successful completion of the request.
The possible values are:
*YES: Access information is updated.
*NO: Access information is not updated.
Specify whether the communications session with the server should be ended before any post-processing program is called.
The possible values are:
*NO: If the server has specified that a user-written program be called to process the received RSF data, and if the server has specified *NO for the DROP parameter on the requester directory entry, the session remains active while the post-processing program is called. Status messages reporting the progress of the post-processing program are returned to your machine.
*YES: The session with the server is ended after the package is received by the server. If the server has specified that a user-written program be called to process the received RSF data, the session is ended before the program is called. The post-processing program is executed asynchronously by the server.
Whether RSF should hang up the phone connection at the completion of the transaction. This parameter is ignored for non-switched connections. Click here for a complete description of this parameter.
The phone number to pass to the server machine when requesting that the server call your machine back. Click here for a complete description of this parameter.
Indicate whether to compress data as it is transmitted. Click here for a complete description of this parameter.
An ad hoc message to be sent to the server along with the RSF request. Click here for a complete description of this parameter.
Enter the qualified name of the save file to send to the remote machine.
This is a required parameter if *SAVF is specified for "Package".
The possible save file values are:
save-file-name: Enter the name of an existing save file.
The possible library values are:
*LIBL: The job library list is used to locate the save file.
*CURLIB: The save file is found in the current library.
library-name: The name of the library containing the save file.
Enter the qualified name of the location list to reference. Location lists are stored as physical file members
Note: If you plan to use the relay distribution option (RELAY(*YES)) or you are sending to a broadcast server ID (Connection method of *BROADCAST), you should ensure that the location list is stored in a library that can be accessed by batch jobs initiated by remote machines as they report the distribution status.
This is a required parameter if *LIST is specified for the Server ID (SERVER) parameter.
The possible values are:
location-list-name: Enter the name of an existing location list.
The possible library values are:
*LIBL: The job library list is used to locate the list.
*CURLIB: The list is found in the current library.
library-name: The name of the library containing the list.
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.
Specify whether to reset the access count and status for all entries in the location list before beginning any transmissions.
This parameter is ignored unless *LIST is specified for the Server ID (SERVER) parameter.
The possible values are:
*YES: The location list is reset.
*NO: The location list is not reset.
Specify whether machines that receive the transmission successfully should forward the transmission on to other locations.
Using relay distribution can greatly reduce the total time required to send a transmission to many locations. Each receiving machine becomes an additional sending machine, while central control remains with the machine on which the send command was originally run.
Notes:
If *YES is specified for this parameter, this
machine will only send to machines that have *YES specified for "Relay to this
machine" (RELAY) in the server directory entry.
If *YES is specified for this parameter, you should ensure that any post-processing or installation procedure on the target machine does not delete the transmitted save file, thus ensuring that the save file is available to be relayed to other locations when the transmission completes. The request data structure passed to post processing programs contains a 1-byte field which indicates whether relay processing was requested or not. (Y = Yes.) See physical file RSDS002 for the layout of the data structure.
This parameter is ignored unless *LIST is specified for the Server ID (SERVER) parameter.
The possible values are:
*NO: Relay distribution is not used. All locations are contacted directly by this machine.
*YES: Relay distribution is used. Receiving machines participate in sending the transmission on to other machines.
When you prompt for command parameters with F4, default name, address and telephone information is filled in for you. These are the same defaults the system uses to send PTF orders via Electronic Customer Support.
The possible values are:
contact information: Enter the appropriate information for contact name, address, and phone.
The following commands are discussed elsewhere in this manual:
Retrieve Package (RTVRSFPKG)
Work With Catalog (WRKRSFCAT)
Copy File Using RSF (CPYFRSF)
Retrieve Objects (RTVOBJRSF)
Send Objects (SNDOBJRSF)
Retrieve Documents (RTVDOCRSF)
Send Documents (SNDDOCRSF)
Create Package (CRTRSFPKG)
For more information about the following commands, prompt the command and press F1 to view the on-line help text:
Change Package (CHGRSFPKG)
Delete Package (DLTRSFPKG)
Rename Package (RNMRSFPKG)
The Send Spooled File (SNDSPLFRSF) command is used to send one or more spooled files to a remote server. The Retrieve Spooled File (RTVSPLFRSF) command is used to retrieve one or more spooled files from a remote server. All spooled file attributes are preserved.
The prompted version of the SNDSPLFRSF command is shown below. Click on the image to see parameter descriptions.
The parameters for the SNDSPLFRSF command are described below.
The name of a server directory entry to be referenced. The entry must have been previously added to the server directory on your machine. This is a required parameter. Click here for a complete description of this parameter.
The name of the spooled file to send. This is a required parameter.
The possible values are:
*ALL: All spooled files are sent that meet the criteria specified by the other parameters for this command.
name: The name of a specific spooled file to send.
The qualified name of a job containing the spooled file to be sent.
The possible values are:
*: The spooled file is found in the current job.
*ALL: Spooled files for all jobs are sent. *ALL is not valid for this parameter unless *ALL is also specified for "Spooled file".
name: The name of the job containing the spooled file.
User
name: The user id associated with the job.
Number
000000-999999: The number for the job.
Enter the number of the spooled file to be sent. This parameter is ignored if *ALL is specified for "Spooled file name".
The possible values are:
*LAST: The last spooled file created with the specified name in the specified job is sent.
*ONLY: The only spooled file created with the specified name in the specified job is sent.
1-9999: Enter the number of the spooled file to send.
Enter the qualified name of the output queue to which the spooled files should be sent.
The possible values are:
*DFT: The spooled files are sent to the server's default output queue, specified in the requester directory entry that refers to your machine. See Adding Requester Directory Entries for more information.
output-queue: Enter the name of the output queue on the server machine to which the spooled files should be sent.
The possible library values are:
*LIBL: The job library list is used to locate the output queue.
library name: The name of the library containing the output queue.
Specify whether to delete the original spooled files after they have been sent.
The possible values are:
*NO: The original spooled files are not deleted.
*YES: The original spooled files are deleted after they have been sent.
Indicate whether to compress data as it is transmitted. Click here for a complete description of this parameter.
The name of the user for which spooled files are sent. This parameter is ignored unless *ALL is specified for "Spooled file".
The possible values are:
*CURRENT: Spooled files for the current user are sent.
*ALL: Spooled files for all users are sent.
name: The name of the user whose spooled files are to be sent.
The qualified name of the output queue containing the spooled files to be sent. This parameter is ignored unless *ALL is specified for "Spooled file".
The possible values are:
*ALL: Spooled files for all output queues are sent.
name: The name of the output queue containing the spooled files to be sent.
The possible library values are
*LIBL: The job library list is used to locate the output queue.
*CURLIB: The current library is used to locate the output queue.
library name: The name of the library containing the output queue.
The form type for spooled files to be sent. This parameter is ignored unless *ALL is specified for "Spooled file".
The possible values are:
*ALL: All spooled files are sent, regardless of their form type.
*STD: Only spooled files with form type *STD are sent.
characters: Only spooled files that match the specified form type are sent.
Select spooled files to be sent which match the specified user data. This parameter is ignored unless *ALL is specified for "Spooled file".
The possible values are:
*ALL: All spooled files are sent, regardless of their user data attribute.
characters: Only spooled files that match the specified user data are sent.
Whether RSF should hang up the phone connection at the completion of the transaction. This parameter is ignored for non-switched connections. Click here for a complete description of this parameter.
The phone number to pass to the server machine when requesting that the server call your machine back. Click here for a complete description of this parameter.
An ad hoc message to be sent to the server along with the RSF request. Click here for a complete description of this parameter.
When you prompt for command parameters with F4, default name, address and telephone information is filled in for you. These are the same defaults the system uses to send PTF orders via Electronic Customer Support.
The possible values are:
contact information: Enter the appropriate information for contact name, address, and phone.
The following command is discussed elsewhere in this manual:
Monitor Output Queue (STRMONOUTQ)
For more information about the following command, prompt the command and press F1 to view the on-line help text:
Retrieve Spooled Files (RTVSPLFRSF)
The Send IFS Objects (SNDIFSRSF) command can be used to send objects in the Integrated Files System (IFS) to another machine. The objects can be sent to the same or to a different directory on the target machine.
User-written exit programs can be called both before and after the objects are sent to further customize the object distribution process.
The prompted version of the SNDIFSRSF command is shown below. Click on the image to see parameter descriptions.
The parameters for the SNDIFSRSF command are described below.
Enter up to 15 specifications defining the objects to be sent. There are three parts to each specification:
The path and name of the objects to send. This can be a path
to a specific object or directory, or a generic name which includes pattern matching characters.
Whether to include or omit the specified objects.
The path and name to use when restoring the objects on the target machine.
This is a required parameter.
The possible Object values are:
*: Objects in the current directory are sent.
~/: Objects in the home directory of the current user are sent.
~user-name/: Objects in the home directory of the specified user are sent.
relative-path-name: A relative path is one that does not begin with a slash. The path is assumed to start in the user's current directory.
full-path-name: A full path begins with a slash. The path specification starts at the root.
generic-name: You may include wild card characters in the last part of the path name to define a pattern that will select multiple objects. An asterisk (*) will match any number of characters. A question mark (?) will match any single character. You must enter two asterisks together to begin the path specification with an asterisk.
The possible Include/Omit values are:
*Include: The specified objects are included.
*OMIT: The specified objects are omitted. You can use an *OMIT specification after an *INCLUDE specification to omit a few objects from the previous specification.
The possible Restore To values are:
*Same: The objects are restored to the same names and directories on the target machine that they had on the source machine.
path-name: Enter the new path and name for the objects.
Note: Only the last directory or file in the path name will be created on the target machine. If any directory in the middle of the path name does not exist on the target, the send will fail.
The name of a server directory entry to be referenced. The entry must have been previously added to the server directory on your machine. This is a required parameter. Click here for a complete description of this parameter.
Specify whether sub-directories should be included with the selection.
The possible values are:
*ALL: All sub-directories in the specified paths are included.
*DIR: The sub-directories within each matching directory are included, but lower-level directories are not included.
*NONE: No sub-directories are included.
*OBJ: Only the specified objects are included. If a directory is specified, objects within the directory are not included.
Specify whether to transmit objects that are currently in use.
The possible values are:
*NO: The request ends in error if any of the objects to be transmitted are currently in use by another job.
*YES: All selected objects are transmitted, whether or not they are in use. The object checkpoints can occur at different times.
*SYNC: All selected objects are transmitted, whether or not they are in use. All object checkpoints occur at the same time.
Enter the OS/400 release level of the target machine, relative to the source machine.
The possible values are:
*CURRENT: The remote server machine is at the same OS/400 release level as the local machine.
*PRV: The target machine is one OS/400 release behind the source machine.
release-level: Enter the OS/400 release level of the remote machine, in the form VxRyMz, where x, y and z are the version, release and mod level respectively. For example: V4R4M0.
Indicate whether to compress data as it is transmitted. Click here