ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzalu_5.4.0.1/rzalurspi2z.htm

219 lines
10 KiB
HTML

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="dc.language" scheme="rfc1766" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<meta name="dc.date" scheme="iso8601" content="2005-09-06" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow"/>
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<title>i5/OS to VM/MVS for remote system printing</title>
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
<link rel="stylesheet" type="text/css" href="ic.css" />
</head>
<body>
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
<a name="rzalurspi2z"></a>
<h4 id="rzalurspi2z">i5/OS to VM/MVS for remote system printing</h4>
<p>The following diagram illustrates i5/OS-to-VM/MVS remote system printing
with SNADS. The values (or names) in the diagram are used in this example. </p>
<div class="mmobj">
<img src="rbaft521.gif" alt="i5/OS-to-VM/MVS remote system printing with SNADS" /></div>
<p>Preparation work must be done on both the source system and target system
for remote system printing to work. The following table provides a list of
things that must be present or created before remote system printing can be
used.</p>
<a name="compar3"></a>
<table id="compar3" width="100%" summary="" border="1" frame="border" rules="all" class="singleborder">
<caption>Table 4. Source system and target system preparation for remote system printing</caption>
<thead valign="bottom">
<tr class="tablemainheaderbar">
<th id="wq182" width="50%" align="left">Source system at V3R1 or later</th>
<th id="wq183" width="50%" align="left">VM/MVS target system</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td headers="wq182">Ensure that Licensed Program 5769-CM1 is installed. This is needed
for communications. For more details about configuring SNADS connections between
these systems, see <a href="../books/c4154101.pdf">SNA Distribution Services</a>
<img src="wbpdf.gif" alt="Link to PDF" />.
<p>&nbsp;</p></td>
<td headers="wq183">NJE configuration for VM/RSCS and JES2 or JES3 for MVS&trade;.
<p>Contact with
the host system will be critical to establishing the correct connection with
VM/MVS. System node name, printer ID, and user ID are some of the information
i5/OS will require.</p></td>
</tr>
<tr>
<td headers="wq182">Line, controller, and device descriptions created
<p>Additional information
for these configuration descriptions can be obtained in <a href="../books/c4154010.pdf">Communications Configuration</a>
<img src="wbpdf.gif" alt="Link to PDF" />.</p>
<p>&nbsp;</p></td>
<td headers="wq183">Communication descriptions must exist or be created to connect the
VM/MVS system to i5/OS. Typically this would be a line, physical unit (similar
to controller), and a logical unit (similar to device). The VM or MVS system configuration
will require information from i5/OS.</td>
</tr>
<tr>
<td headers="wq182">Identify the user profile to be used for remote system printing.</td>
<td headers="wq183">This user must also exist on the target system if *USER is specified
on the RMTPRTQ parameter on i5/OS.</td>
</tr>
<tr>
<td headers="wq182">Set up the SNADS network.
<ul>
<li>Create distribution queues and routing entries using the Configure Distribution
Services (CFGDSTSRV) command.
<ul>
<li>Create a distribution queue.</li>
<li>Create a routing entry and associate the target system name (VM3) with
the distribution queue.</li></ul></li>
<li>Add users to the system directory. Use the Add Directory Entry (ADDDIRE)
command.
<ul>
<li>Add a directory entry for the QNETSPLF user profile. (This entry is the
user ID used by SNADS on the source system.)
<dl class="parml">
<dt class="bold">User ID</dt>
<dd>This must be QNETSPLF.
</dd>
<dt class="bold">Address</dt>
<dd>This is the name of the source system (SYSNMD5T).
</dd>
<dt class="bold">User profile</dt>
<dd>This must be QNETSPLF.
</dd>
<dt class="bold">System name</dt>
<dd>This is the name of the source system (*LCL).
</dd>
<dt class="bold">System group</dt>
<dd>Not used in this example.
</dd>
</dl></li>
<li>Add a directory entry for QNETSPLF. (This entry is the user ID used by
SNADS to route to the target system.)
<dl class="parml">
<dt class="bold">User ID</dt>
<dd>This must be QNETSPLF.
</dd>
<dt class="bold">Address</dt>
<dd>This is the name of the target system (VM3).
</dd>
<dt class="bold">User profile</dt>
<dd>This must be *NONE.
</dd>
<dt class="bold">System name</dt>
<dd>This is the name of the target system (VM3).
</dd>
<dt class="bold">System group</dt>
<dd>Not used in this example.
</dd>
</dl></li></ul></li></ul></td>
<td headers="wq183">For MVS, identification of the iSeries server must be entered in the JCL or
JES and associated with a printer defined to the MVS system.
<p>For VM, identification of the iSeries server
must be entered in RSCS and associated with a printer defined to the VM system.</p></td>
</tr>
<tr>
<td headers="wq182">Create a remote output queue for remote system printing.
<p>Use the
Create Output Queue (CRTOUTQ) command.</p></td>
<td headers="wq183">&nbsp;</td>
</tr>
<tr>
<td headers="wq182">When sending spooled output files to VM/MVS, the default forms type
must be STANDARD (not to be confused with *STD for i5/OS). The forms type
can be changed by overriding the printer file used to create the spooled output
files. Also, you could use the Change Spooled File Attributes (CHGSPLFA)
command and change the forms type parameter value to standard.</td>
<td headers="wq183">&nbsp;</td>
</tr>
</tbody>
</table>
<p><span class="bold">Source system activity - creating the remote output queue</span></p>
<p>The result of using this example would be spooled output files sent to
the system printer on the target system (VM3). </p>
<a name="wq184"></a>
<div class="notetitle" id="wq184">Note:</div>
<div class="notebody">When a remote
output queue is created, writers are automatically started to it if the AUTOSTRWTR
parameter value is other than *NONE.</div>
<p>Type CRTOUTQ and press F4 (Prompt). The following display appears. Type
the values shown and press the Enter key. The remote output queue TEST1 is
created. The other parameter values are needed to ensure connection and delivery
to the designated system. </p>
<pre class="screen"><span class="bold"> Create Output Queue (CRTOUTQ)</span>
Type choices, press Enter.
Output queue . . . . . . . . . . <span class="bold-italic">RMTOUTQ</span> Name
Library . . . . . . . . . . . <span class="italic">MYLIB</span> Name, *CURLIB
Maximum spooled file size: <span class="italic">&nbsp;</span>
Number of pages . . . . . . . <span class="italic">*NONE</span> Number, *NONE
Starting time . . . . . . . . <span class="italic">&nbsp;&nbsp;&nbsp;&nbsp;</span> Time
Ending time . . . . . . . . . <span class="italic">&nbsp;&nbsp;&nbsp;&nbsp;</span> Time
+ for more values <span class="italic">&nbsp;</span>
Order of files on queue . . . . <span class="italic">*FIFO</span> *FIFO, *JOBNBR
Remote system . . . . . . . . . <span class="italic">VM3</span>
Remote printer queue . . . . . <span class="italic">*SYSTEM</span>
Queue for writer messages . . . <span class="italic">QSYSOPR</span> Name, QSYSOPR
Library . . . . . . . . . . . <span class="italic">&nbsp;&nbsp;&nbsp;&nbsp;</span> Name, *LIBL, *CURLIB
Connection type . . . . . . . . <span class="italic">*SNA</span> *SNA, *IP
Destination type . . . . . . . . <span class="italic">*S390</span> *OS400, *OS400V2, *PSF2...
VM/MVS class . . . . . . . . . . <span class="italic">C</span>
FCB . . . . . . . . . . . . . . <span class="italic">FCB2</span>
Text 'description' . . . . . . . <span class="italic">i5/OS to VM System named VM3</span>
<span class="bold"> Bottom</span>
F3=Exit F4=Prompt F5=Refresh F10=Additional parameters F12=Cancel
F13=How to use this display F24=More keys
</pre>
<p>To begin sending spooled output files from the RMTOUTQ remote output queue,
run the Start Remote Writer (STRRMTWTR) command by typing STRRMTWTR and pressing
F4 (Prompt).</p>
<p>The following display appears. Type RMTOUTQ and press the Enter key.
Spooled output files are then sent to the printer designated as the system
printer on the target system (VM3). </p>
<pre class="screen"><span class="bold"> Start Remote Writer (STRRMTWTR)</span>
Type choices, press Enter.
Output queue . . . . . . . . . . <span class="bold-italic">RMTOUTQ</span> Name, *ALL
Library . . . . . . . . . . . <span class="italic">MYLIB</span> Name, *LIBL, *CURLIB
Queue for writer messages . . . <span class="italic">*OUTQ</span> Name, *OUTQ, *REQUESTER
Library . . . . . . . . . . . <span class="italic">*LIBL</span> Name, *LIBL, *CURLIB
Form type options:
Form type . . . . . . . . . . <span class="italic">*ALL</span> Form type, *ALL, *STD, *FORMS
Message option . . . . . . . . <span class="italic">*NOMSG</span> *NOMSG, *INQMSG, *MSG...
<span class="bold"> Bottom</span>
F3=Exit F4=Prompt F5=Refresh F10=Additional parameters F12=Cancel
F13=How to use this display F24=More keys
</pre>
<p><span class="bold">Target system activity - printing spooled output files
from the source system</span></p>
<p>The spooled files were sent to the system printer on the target system
(VM3).</p>
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
</body>
</html>