02.05.2013 Views

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Setting Up for SNADS Distribution<br />

Setting Up for SNADS Distribution<br />

<strong>Implementer</strong> works with SNA Distribution Services (SNADS) to distribute changes to remote<br />

iSeries systems. If you are not using SNADS for distribution (for example, you are using<br />

SDMCom) you can bypass this section.<br />

The host iSeries system requires SNADS directory entries for each user profile that sends and<br />

receives remote distributions using SNADS. Before starting the following task, you must<br />

have the remote location name of the iSeries system you distribute to. You must use the<br />

remote location name, not the system name. To determine the remote location name, use the<br />

DSPAPPNINF (Display APPN Information) command if you use APPN, or use the<br />

DSPDEVD (Display Device Description) command for the APPC device that connects to the<br />

remote.<br />

NOTE The remote location name is usually the same as the system name of the<br />

remote. To prevent errors, use the above commands to ensure you use the correct<br />

location name.<br />

Add Directory Entries for Sending User Profiles<br />

A SNADS directory entry must exist for each host user profile defined in <strong>Implementer</strong> that<br />

has authority to distribute changes to remote systems (these user profiles are often already<br />

enrolled).<br />

To create the directory entry for a user not currently enrolled in SNADS<br />

Issue the following command:<br />

ADDDIRE USRID(user-profile local-system-name)<br />

USRD('Text description for the user')<br />

USER(user-profile)<br />

Add Directory Entries for Receiving User Profiles<br />

A SNADS directory entry must exist for each iSeries you distribute changes to. You can<br />

create the directory entry for receiving user profiles in any of three ways:<br />

Use directory entry USER(*ANY *ANY) to allow distribution to any user on the iSeries<br />

system identified to SNADS.<br />

Use directory entry USER(*ANY remote-location-name) to allow distribution to any user<br />

on the iSeries that matches the remote-location-name.<br />

If neither of these directory entries exists, you can create the following <strong>Implementer</strong>specific<br />

directory entry. Only one directory entry is required for the remote location.<br />

Specify this directory when defining the remote iSeries in Network Configuration. It is<br />

usually for user profile MWIPROD, as all network files are sent to that directory entry on<br />

the remote.<br />

179

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!