Configuring SNADS and Setting Up SNA Distribution Services

Resolving The Problem

This document explains the SNADS configuration process and is intended to help you:

	Provide step-by-step instructions on how to configure Systems Network Architecture Distribution Services (SNADS)
	Clarify which system values to use for the Address or System Name parameters in a local and remote directory entry
	Explain the difference between a Local Directory Entry and a Remote Directory Entry and guide you through the process of creating these entries
	Show you how to configure a Routing Table Entry and how to configure a Distribution Queue
	Provide a list of common SNADS-related CL commands that can be used to configure SNADS and that can be used to send distributions after you configure SNADS

SNADS Requirements

For SNADS to operate properly, it requires the following on the IBM System i system:

	Communications line, controller, and device descriptions configured for APPC or APPN support. For more information about configuring line, controller, and device descriptions for APPC, see the APPC Programming manual. For more information about APPN configuration, see the APPN Support manual.
	The IBM-supplied subsystem QSNADS must be active. To start this subsystem, on the operating system command line type the following: STRSBS SBSD(QSNADS) Press the Enter key.
	The IBM-supplied subsystem QSYSWRK must be active. To start this subsystem, on the operating system command line type the following: STRSBS SBSD(QSYSWRK) Press the Enter key.
	The Mail Server Framework job QMSF found under subsystem QSYSWRK must be active. To start this job, on the operating system command line type the following: STRMSF Press the Enter key.
	The Object Distribution job QNFTP found under subsystem QSNADS must be active. This job should automatically start when the subsystem QSNADS is started. If it is not started, try ending and then starting subsystem QSNADS. If problems persist, call the IBM Rochester Support Center, and report a SNADS problem.
	There must be a successful communications link test between the two systems you plan to set up SNADS for. Before configuring SNADS, test the communications link by starting a display station pass-through session from the source system to the target system. To test the communications link, start a display station pass-through session using the same RMTLOCNAME, LCLLOCNAME, MODE, and RMTNETID parameters you plan to use when configuring your Distribution Queue for SNADS. In other words, use the same RMTLOCNAME, LCLLOCNAME, MODE, and RMTNETID parameters in your test as you plan to use with SNADS. For example, a user may start the a Display Station Pass-Through session by typing the following on the operating system command line: STRPASTHR RMTLOCNAME(SYSB) MODE(BLANK) + LCLLOCNAME(SYSA) RMTNETID(APPN) (See Note 1.) Press the Enter key. If pass-through works with the selected parameters, this user is ready to configure SNADS and should use these parameter values when configuring the distribution queue. If pass-through does not work with the selected parameter values, call the IBM Rochester Support Center, and report a display station pass-through problem. Notes: 1 The parameters cited in the example above (RMTLOCNAME, MODE, LCLLOCNAME, and RMTNETID) may be different for each iSeries family system connection. The iSeries family system connection may not match the parameters described above. To verify the actual RMTLOCNAME, MODE, LCLLOCNAME, and RMTNETID parameters, display the device description you plan to use for SNADS. 2 For more information about configuring display station pass-through, refer to the Remote Work Station Support manual.

Configuring SNADS The process of configuring SNADS is divided in the following steps: I. Adding a Local System Distribution Directory Entry II. Adding a Remote System Distribution Directory Entry III. Configuring Distribution Services Note: This is a basic SNADS configuration. There are many ways to configure SNADS. For advanced functions, refer to the SNA Distribution Services manual.

I. Adding a Local System Distribution Directory Entry

A Local System Distribution Directory Entry authorizes an individual local user to distribute and receive objects. A local user is defined in the SNA Distribution Services manual as a person who has a user profile on your local system and whose system has the same name as your system.

Using and managing the System Distribution Directory can be simplified by assigning the User ID parameter in the Directory Entry the same value as the User Profile for the user profile which the entry represents. However, because there are different naming conventions for these fields, you must limit the User Profile parameter in the user profile to 8 characters. If your User Profile is more than 8 characters, refer to the SNA Distribution Services manual, Chapter 3.

The suggested way for assigning user IDs is to use the User Profile parameter from the profile for the user in the User ID field in the Directory Entry. In addition, the Address field and the System Name field in the Directory Entry should be completed with the Current System Name parameter found in the Network Attributes for the local system (DSPNETA).

Example 1: Creating a Local Directory Entry

User Jane Smith has a user profile JANE in her local system called SYSA (Current System Name is SYSA). She wants to add a new Local System Directory Entry. If user JANE types on the operating system command line WRKDIRE and selects Option 1 on first empty line to Add a new entry, the new local entry looks similar to the following:

Add Directory Entry Type choices, press Enter.                                                                                                                                    User ID/Address . . . .   JANE      SYSA                                     Description . . . . . .   Jane Smith's Local Directory Entry                   System name/Group . . .   SYSA                   F4 for list                  User profile  . . . . .   JANE                   F4 for list                  Network user ID . . . .

Example 2: Different Way to Create a Local Directory Entry

User Jane Smith has a user profile JANE in her local system called SYSA (Current System Name is SYSA). She wants to add a new Local System Directory Entry. If user JANE types the ADDDIRE command on the operating system command line, the new local entry looks similar to the following:

Add Directory Entry (ADDDIRE)                          Type choices, press Enter.                                                                                                                                   User identifier:                                                                User ID  . . . . . . . . . . .   JANE          Character value                Address  . . . . . . . . . . .   SYSA          Character value               User description . . . . . . . .   Jane Smith's Local Directory Entry                                                                                         User profile . . . . . . . . . .   JANE          Name, *NONE                   System name:                                                                    System name  . . . . . . . . .   SYSA          Character value, *LCL, *PC...  System group . . . . . . . . .                 Character value               Network user ID  . . . . . . . .   *USRID

                               

Adding a New Local Directory Entry

To add a new local directory entry, do the following:

1.	On the operating system command line of your local System i™ system, type the following: DSPNETA Press the Enter key. You are shown the Display Network Attributes screen.
2.	Copy down the value of the Current System Name parameter from the local Network Attributes of the iSeries family system. Press F3 to Exit the Display Network Attributes screen.
3.	On the operating system command line of your local System i system, type the following: ADDDIRE Press the Enter key. You are shown the Add Directory Entry (ADDDIRE) screen.
4.	In the User ID field, type the user ID for the local user who you want to authorize to distribute objects. It is highly suggested (for simplicity purposes) that the User Profile for the user be used.
5.	In the Address field, type the local system name you copied in Step 2.
6.	In the User Description field, type a description that helps identify the user specified in Step 4 (possibly the full name of the user).
7.	In the User Profile field, type the User Profile for the user who you want to authorize to distribute objects. This must be a valid user profile on the local iSeries family system. If a valid and existing user profile is not used, a message is issued at the bottom of your screen when you attempt to create the entry. CPF2204: User profile not found.
8.	In the System Name field, type the local system name you copied in Step 2.
9.	In the System Group field, leave it blank. Do not type anything in this field.
10.	Press the Enter key to create the new local directory entry. A message is issued at the bottom of the screen confirming that the new entry was added to the directory.

II. Adding a Remote System Distribution Directory Entry

A Remote System Distribution Directory Entry provides initial route parameters used by SNADS to send a distribution to a remote user in a remote system. A remote user is defined in the SNA Distribution Services manual as a person who has a user profile on a remote system and whose system name is not the same system name as your (local) system.

There is no difference between the procedure for adding remote users individually and adding local users except that the System Name field for a remote directory entry contains the name of the remote system. The remote user must be also enrolled as a local user on the remote system.

The following are suggested ways to assign user IDs in a remote system distribution directory entry. The first suggested way is to create an individual remote system distribution directory entry for every remote user. However, to reduce the number of directory entries required for remote users, create one remote directory entry for all remote users. Do this by using a default entry where the User ID field is *ANY rather than a individual user ID.

Example 3: Creating an Individual Remote Directory Entry

User Jane Smith wants to add a new remote system directory entry so she can send distributions to remote user Joe Brown. Remote user Joe Brown has a user profile JOE in the remote system called SYSB (Current System Name of the remote system is SYSB). If user JANE types on the OS/400 or i5/OS command line WRKDIRE and selects Option 1 on the first empty line to Add a new entry, the new remote entry for Joe Brown should look like the following:

Add Directory Entry Type choices, press Enter.                                                                                                                                    User ID/Address . . . .   JOE       SYSB                                     Description . . . . . .   Joe Brown's Remote Directory Entry                   System name/Group . . .   SYSB                   F4 for list                  User profile  . . . . .                          F4 for list                  Network user ID . . . .

  Example 4: Different Way to Create an Individual Remote Directory Entry

User Jane Smith wants to add a new Remote System Directory Entry so she can send distributions to remote user Joe Brown. Remote user Joe Brown has a user profile JOE in the remote system called SYSB (Current System Name of the remote system is SYSB). If user JANE types ADDDIRE on the operating system command line to add a new entry, the new entry looks similar to the following:

Add Directory Entry (ADDDIRE)                          Type choices, press Enter.                                                                                                                                   User identifier:                                                                User ID  . . . . . . . . . . .   JOE           Character value                Address  . . . . . . . . . . .   SYSB          Character value               User description . . . . . . . .   Joe Brown's Remote Directory Entry                                                                                   User profile . . . . . . . . . .                 Name, *NONE                   System name:                                                                    System name  . . . . . . . . .   SYSB          Character value, *LCL, *PC...  System group . . . . . . . . .                 Character value               Network user ID  . . . . . . . .   *USRID

Example 5: Creating One Remote Directory Entry for All Remote Users (*ANY)

User Jane Smith wants to add a new Remote System Directory Entry so she can send distributions to all remote users in the remote system called SYSB (Current System Name of the remote system is SYSB) independent of their user profiles. If user JANE types WRKDIRE on the operating system command line of her local system and selects Option 1 on the first empty line to Add a new entry, the new remote entry for all remote users at system SYSB should look like the following:

Add Directory Entry Type choices, press Enter.                                                                                                                                    User ID/Address . . . .   *ANY      SYSB                                     Description . . . . . .   Remote Directory Entry for all users at SYSB                   System name/Group . . .   SYSB                   F4 for list                  User profile  . . . . .                          F4 for list                  Network user ID . . . .

Example 6: Different Way to Create One Remote Directory Entry for All Remote Users (*ANY)

User Jane Smith wants to add a new remote system directory entry so she can send distributions to all remote users in the remote system called SYSB (Current System Name of the remote system is SYSB) independent of their user profiles. If user JANE types ADDDIRE on the operating system command line to add a new entry, the new entry looks similar to the following:

Add Directory Entry (ADDDIRE)                          Type choices, press Enter.                                                                                                                                   User identifier:                                                                User ID  . . . . . . . . . . .   *ANY          Character value                Address  . . . . . . . . . . .   SYSB          Character value               User description . . . . . . . .   Remote Directory Entry for all users at SYSB                                                                                   User profile . . . . . . . . . .                 Name, *NONE                   System name:                                                                    System name  . . . . . . . . .   SYSB          Character value, *LCL, *PC...  System group . . . . . . . . .                 Character value               Network user ID  . . . . . . . .   *USRID

Adding a New Remote Directory Entry

To add a new remote directory entry, do the following:

1.	On the operating system command line of your local System i system you want to send distributions to, type the following: DSPNETA Press the Enter key. You are shown the Display Network Attributes screen.
2.	Copy down the value of the Current System Name parameter for the Network Attributes for remote iSeries family system. Press F3 to Exit the Display Network Attributes screen.
3.	On the operating system command line of the local iSeries family system, type the following: ADDDIRE Press the Enter key. You are shown the Add Directory Entry (ADDDIRE) screen. You have the following options for completing the User ID field: Type an individual user profile in the User ID field, or type *ANY in the User ID field. Please read both options described below, select one of them, and follow the appropriate directions: a. In the User ID field, type the user ID for the remote user who you want to send distributions to. It is highly suggested (for simplicity purposes) that the User Profile for the user be used. b. In the User ID field, type *ANY rather than an individual remote user ID. Typing *ANY in the User ID field is recommended. It is not necessary to create one entry for every remote user. This simplifies the setup and reduces the number of entries in the System Distribution Directory. If you type *ANY in the User ID field, your entry looks similar to Example 6 above.
4.	In the Address field, type the remote system name you copied down in Step 2.
5.	In the User Description field, type a description that helps identify the user specified in Step 3 (possibly the full name of the user or the remote system).
6.	Leave the User Profile field blank.
7.	In the System Name field, type the remote system name you documented in Step 2. Note: The System Name field is very important. The System Name field value must be the name of the Routing Table you will create in Step 21 of the Configuring Distribution Services section below. Therefore, document the System Name field value for later reference.
8.	Leave the System Group field blank.
9.	Press the Enter key to create the new remote directory entry. You may get a message at the bottom of your screen stating System name and group not found. Disregard the message. Press the Enter key to confirm and create the remote directory entry. You will get a message at the bottom of your screen stating that the new entry was added to the directory.

III. Configuring Distribution Services

1.	Start a display station pass-through session from the source system to the target by using the STRPASTHR command. For example, on the OS/400 or i5/OS command line, type the following: STRPASTHR RMTLOCNAME(SYSB) MODE(BLANK) + LCLLOCNAME(SYSA) RMTNETID(APPN). Press the Enter key. If pass-through works, you will see a sign-on screen at the target system. If pass-through does not work with the selected parameter values, ensure you are using the correct parameter values or call the IBM Rochester Support Center, and report a display station pass-through problem.
2.	Sign on the target system.
3.	End the display station pass-through session. On the operating system command line on the target system, type the following: ENDPASTHR Press the Enter key. You should be back to the command line of the source system.
4.	Press F9 to retrieve the STRPASTHR command used to start the display station pass-through session to the target system.
5.	Press F4 to prompt the STRPASTHR command used to start the display station pass-through session to the target system. You should be at the Start Pass-Through (STRPASTHR) screen.
6.	Document the values of the following parameters from the Start Pass-Through (STRPASTHR) screen: Remote Location Mode Local Location Remote Network Identifier a If the Local Location parameter value on the Start Pass-Through (STRPASTHR) screen is *NETATR, use the DSPNETA command, and document the value of the Default Local Location parameter from the network attributes on the source system. b. If the Remote Network Identifier parameter value on the Start Pass-Through (STRPASTHR) screen is *NETATR, use the DSPNETA command, and copy down the value of the Local Network ID parameter from the network attributes on the source system. c. Copy parameters below:

Start Pass-Through (STRPASTHR) Screen	Network Attributes
Remote Location =>
Local Location =>	Default Local Location =>
Remote Network Identifier =>	Local Network ID =>
Mode =>

7. 8.	Once you have documented the above parameters, press F3 to return to an operating system command line. Before continuing, verify the version of the operating system of the iSeries family system. Beginning at V4RxMx, the QMSF job must be ended before adding/removing/changing a routing table entry. If the iSeries family system is at V4R1M0 or later, on the operating system command line, type the following: ENDMSF OPTION(*IMMED) Press the Enter key
9.	On the operating system command line, type the following: CFGDSTSRV Press the Enter key. You are shown the Configure Distribution Services screen.
10.	Select Option 1 and the Enter key to configure distribution queues. You are shown the Configure Distribution Queues screen.
11.	Press F6 to Add distribution queue. You are shown the Add Distribution Queue screen.
12.	In the Queue parameter, type the name of the queue to add. The name of the target system is usually a good choice. Write down the queue name. This is the queue in which distributions are stored prior to sending to the target system.
13.	For the Queue Type parameter, type *SNADS.
14.	For the Remote Location Name parameter, type the Remote Location parameter value from the Start Pass-Through (STRPASTHR) screen in Step 6.
15.	In the Mode parameter, type the Mode parameter value copied from the Start Pass-Through (STRPASTHR) screen in Step 6.
16.	In the Remote Net ID parameter, type the Remote Network Identifier parameter value copied from the Start Pass-Through (STRPASTHR) screen in Step 6. Note: If the Remote Network Identifier parameter value copied from the Start Pass-Through (STRPASTHR) screen is *NETATR, type the Local Network ID parameter value copied from the network attributes on the source system.
17.	In the Local Location Name parameter, type the Local Location Name parameter value copied from the Start Pass-Through (STRPASTHR) screen in Step 6. Note: If the Local Location parameter value copied from the Start Pass-Through (STRPASTHR) screen is *NETATR, type the Default Local Location parameter value copied from the network attributes on the source system.
18.	Press the Enter key to add the distribution queue. You get a message at the bottom of the screen stating the queue was added.
19.	Press F12 to return to the Configure Distribution Queues screen. Press F12 again to return to the Configure Distribution Services screen.
20.	Select Option 2, and press the Enter key to configure the routing table. You are shown the Configure Routing Table screen.
21.	Press F6 to Add routing table entry. This takes you to the Add Routing Table Entry screen. A routing table entry is used to identify the name of the Distribution Queue used when sending a distribution to another user (as you will see in Step 24).
22.	In the System Name/Group parameter, type the same value typed in Step 7 in Section II, Adding a Remote System Distribution Directory Entry. The value of the System Name/Group parameter in the routing table entry must be exactly the same value used in the System Name and Group fields used when you created the remote entry in Step 8 of the section above. o When user Jane Smith created a Remote Directory Entry to allow her to send distributions to remote system SYSB (see Examples 3, 4, 5, or 6 above), the System Name value in the remote directory entry used was SYSB, and Group value was blank. When user Jane Smith creates a routing table entry, the System Name parameter must be SYSB, and the Group parameter must be blank. o The System Name and Group fields of a Remote Distribution Directory Entry are used to identify the name of a Routing Table Entry used by SNADS to route distributions for the remote user. Therefore, if the System Name and Group fields of a Remote Distribution Directory Entry do not match the System Name and Group of any Routing Table Entry, the distributions do not reach a Distribution Queue and SNADS does not work properly.
23.	In the Description parameter, type an appropriate description to identify this routing table entry.
24.	In the Queue Name parameters under the Fast (Service Level), type the name of the queue created in Step 11 of this section. In the Queue Name parameters under the Status (Service Level), type the name of the queue created in Step 11 of this section. In the Queue Name parameters under the Data high (Service Level), type the name of the queue created in Step 11 of this section. In the Queue Name parameters under the Data low (Service Level), type the name of the queue created in Step 11 of this section.
25.	The Maximum Hops parameters retain the default values of *DFT.
26.	Press the Enter key to add the routing table entry. You get a message at the bottom of the screen stating the entry was added.
27. 28.	Press F3 to return to the operating system command line. If the iSeries family system is at V4R1M0 or later, and the QMSF job was ended in step 8 above, it must be restarted at this point. On the operating system command line, type the following: STRMSF MSGOPT(*RESUME) Press the Enter key
29.	Choose one of the commands below to test the new configuration. Generally, sending a network message to a remote user using the SNDNETMSG command is sufficient. Remember the remote user receiving the message must have a Local System Distribution Directory Entry in the system that authorizes distribution and receipt of objects. You must follow the instructions on section I Adding a Local System Distribution Directory Entry and add a Local System Directory Entry in the remote system for every user you intend to send distributions to. For instructions on adding a Local System Directory Entry, see section I Adding a Local System Distribution Directory Entry above.

Common CL Commands Related to SNADS

Following are some of the most common CL commands related to SNA Distribution Services. Use these commands to send, receive, display, change, add, remove, or work with SNADS functions:

Configuration Commands

ADDDIRE: The Add Directory Entry (ADDDIRE) command allows you to add new entries to the system distribution directory. The directory contains information about a user; for example, such as the user ID and address, system name, user profile name, mailing address, telephone, number, and other user information.

ADDDSTQ: The Add Distribution Queue (ADDDSTQ) command allows you to add an entry to the distribution services queue table. Distribution queues are used to store distributions before they are sent or forwarded to other systems.

ADDDSTRTE: Adds an entry to the distribution services routing table. Adds an entry to the distribution services secondary system name table. Secondary system name entries identify alternative (alias) names for the system.

ADDDSTSYSN: The Add Distribution Secondary System Name (ADDDSTSYSN) command allows you to add an entry to the distribution services secondary system name table. The table contains the names of all of the alternate (or alias) system names for which this system receives and may redirect distributions. The SNA distribution services (SNADS) function automatically directs distributions with the local system as the destination system name, so the local system cannot be added to the secondary system name table.

CFGDSTSRV: The Configure Distribution Services (CFGDSTSRV) command changes the configuration of the distribution network. The user can add, change, remove, and display entries from the distribution queues table, the routing table, and the secondary system name table.

Management Commands

DSPDSTLOG: Provides an interface to the QSNADS journal. The QSNADS journal contains entries that track SNADS operations that were performed on the system, including sending, receiving, and routing distributions and configuration changes.

HLDDSTQ: The Hold Distribution Queue (HLDDSTQ) command prevents a distribution queue from being sent.

INZDSTQ: Resets the status of a distribution queue and optionally deletes all distributions on that queue. Also allows queues to be cleaned up before changes are made to a network.

RLSDSTQ: The Release Distribution Queue (RLSDSTQ) command releases a distribution queue from held status and allows it to be sent.

STRMSF: The Start Mail Server Framework (STRMSF) command starts the mail server framework jobs (QMSF) in the system work subsystem (QSYSWRK).

WRKDIRE: The Work with Directory Entries (WRKDIRE) command allows you to work with a set of panels to view, add, change, and remove entries in the distribution directory. When the WRKDIRE command is entered, the system shows either one or all of the entries in the system distribution directory, depending on the parameters specified. If the parameter specified applies to more than one directory entry, the system displays a list of directory entries. If the parameter identifies a specific directory user, the system displays a list of entries for which that user has authority.

Restriction: Security administrator authority (*SECADM) is required to update all entries in the directory. Restrictions on the data entries that can be updated apply when this command is run without *SECADM authority. General access to view and print the directory is provided by the DSPDIRE command.

WRKDSTQ: The Work with Distribution Queue (WRKDSTQ) command displays and controls the distribution requests on the Systems Network Architecture distribution services (SNADS) distribution queues.

Send Distribution Commands

SNDDST: The Send Distribution (SNDDST) command allows you to send a distribution to a user, to a list of users, or to a distribution list.

SNDDSTQ: The Send Distribution Queue (SNDDSTQ) command is used to send a distribution queue's entries when the distribution queue is configured to be manually started but no operator is available. It is used to override any distribution queue scheduling attributes and begin sending a queue's entries immediately. It is also used to restart a SNADS sender job that failed abnormally. The SNDDSTQ command is primarily intended for use in a batch CL program. The SNDDSTQ command enables the same functions as Option 2 (Send distribution queue) on the Work with Distribution Queue (WRKDSTQ) command main list panel. The SNDDSTQ command allows the functions to be started from a batch job instead of interactively.

SBMNETJOB: The Submit Network Job (SBMNETJOB) command sends an input stream to another user on the SNADS network. (The input stream is sent to another user where it can be filed, submitted, or rejected.) When the input stream arrives, its placement is governed by the job action (JOBACN) network attribute. If the value of JOBACN is *SEARCH, the entry in the network job table at the receiving system is used to determine the action taken. At the receiving system, the job may be submitted immediately, filed for placement by the receiving user, or rejected. When the input stream arrives at the destination system, a message is sent to both the recipient of the input stream as well as the originator of the input stream stating that the input stream arrived. This command can only be used to send a batch input stream to a user on a remote system.

SNDNETF: The Send Network File (SNDNETF) command sends a save file or a member of a physical database file to another user on the local system or on a remote system through the SNADS network. This command can be used to: send data files to a user; send source files to a user (source sequence information is kept in the file sent); send other object types stored in a save file to a user.

SNDNETMSG: The Send Network Message (SNDNETMSG) command sends a message to another user on the local or a remote system through the SNADS network. This message is sent as an informational message to the message queue that is defined for the recipient on the receiving system.

SNDNETSPLF: The Send Network Spooled File (SNDNETSPLF) command sends a spooled file to another user on the local system or on a remote system on the SNADS network. The file is placed on the output queue that is specified in the user profile of the user to whom the spooled file was sent. When the file arrives at the destination system, a message is sent to both the recipient and sending user notifying them of the arrival of the spooled file.

Other Important Commands

RCVNETF: The Receive Network File (RCVNETF) command receives a network file and copies the records into a physical database file or a save file. Once the file has been received, it is removed from the queue of network files. If the original file is a save file, it must be received into a save file. Before a file can be received, the file specified by the TOFILE parameter must already exist. When a source physical file is sent, the source sequence number and change date in positions 1 through 12 of the record are sent with the file. These are kept if the file is received into a source physical file, and are truncated if the file is received into a nonsource physical file. When a file that was originally a nonsource physical file is received into a source physical file, the source sequence numbers are created and placed in front of the records. If the file is a physical file, the record length of the to-file must be at least as large as the record length of the original file. If the record length of the to-file is larger than that of the original file, the records are padded to the end with the default record value for the to-file.

WRKNETF: The Work with Network Files (WRKNETF) command displays or prints a list of files that have arrived for a user, or creates an output file containing a list of the files. When the list of network files is shown, a user can either receive the file into a user file, delete the file, browse the file (not valid for save files) or submit files (submit the input stream). (Also not valid for save files).

WRKNETJOBE: The Work with Network Job Entry (WRKNETJOBE) command shows the network job entries. There is one entry for each user or distribution group who can submit jobs to this system. This entry is used to determine whether the input stream is automatically submitted, placed on the queue of network files for a user, or rejected. This entry also specifies the user profile that is used for checking the authority to the job description referred by the batch job.