HP-UX SNAplus2 RJE User's Guide

SNAplus2 RJE Components and Operation
Processing Output Data
Chapter 360
• The usr card must be on a single line.
• The usr card may not contain any tabs or blanks.
• The characters “usr” in the usr card are not case sensitive and will be
found if typed in all capital letters. If the entire usr card is in
uppercase, upon receipt by RJE, rjeusr or rjeusrpad folds the
entire card to lowercase.
• The contents of the usr card are case sensitive. The logon and place
can be in either uppercase or lowercase, but you are responsible for
making sure that the case remains the same during the queuing
process. Refer to the command description of “snaprjesend” in
Chapter 4.
• A usr card can be located anywhere on a line, with any characters
preceding it and following it. For example, it is convenient to include
a usr card in a JCL comment as follows:
//* a comment usr=(bc,/users/bc,41) more...
• If more than one usr card is included in a file coming back from the
SNA host, only the first one will be used for routing and notification.
• The path name must be the full path name or be relative to the logon
directory for logon . Do not use metacharacters such as “˜”.
• If the output is not ASCII, the product will not be able to scan for a
usr card. Therefore, the output will not be routed. This can happen if
the -b option is used with the snaprjesend command or if the
output is not translated to ASCII when it is received from the SNA
host.
NOTE If your logon , as listed in the usr card, does not match your logon
entry in /etc/passwd, you will not receive notification that the file
has been received from the SNA host computer, regardless of the
notification code you may have specified. A warning will also be
logged in the audit log file in this case.
Example of usr Cards
The following example is an illustration of a file called testfile which a
user is sending to an SNA host computer. The JCL commands in
testfile specify that the host will return two files to the HP 9000