HPlogo Using NS 3000/iX Network Services: HP 3000 MPE/iX Computer Systems > Chapter 3 Remote File Access

Interactive Access

» 

Technical documentation

Complete book in PDF
» Feedback

 » Table of Contents

 » Index

In order to access a remote file or device interactively, you must first issue a FILE command that specifies the remote location of the file. However, you cannot indicate the location directly in the MPE/iX command or subsystem command that accesses the file.

Example 1

Let's say that you wish to print a text file named DOCUMENT on a line printer connected to a remote HP 3000 computer. You are editing the text file on your local system. After defining an environment on the remote node, you can issue a local FILE command at the MPE/iX prompt that designates the line printer as a remote device and specifies the environment in which it exists. You must also log on to the remote node:

   DSLINE NIKOLAI
FILE REMPRINT;DEV = NIKOLAI#LP
REMOTE HELLO NSUSER.NSACCT

You can then send your finished TDP file to the remote line printer as follows. The local MPE/iX and TDP prompts are shown, and user input is underlined for clarity.

   :RUN TDP.PUB.SYS
/FINAL FROM DOCUMENT TO *REMPRINT

Example 2

   DSLINE NIKOLAI
REMOTE HELLO USER.ACCT
FILE SOURCE=XYZ:NIKOLAI
PASCAL *SOURCE

You may want to compile a remote Pascal source file on your local system. This is how you can do it from the MPE/iX prompt:

Example 3

Let's assume that you have created a session on a remote node by typing at the MPE/iX prompt:

   DSLINE NIKOLAI
REMOTE HELLO USER.ACCT

In order to access a file on your local node, you may use the $BACK specification. Here's an example of that method. The local and remote MPE/iX prompts are shown, and user input is underlined for clarity.

   :REMOTE
NIKOLAI#FILE SOURCE=XYZ:$BACK
NIKOLAI#PASCAL *SOURCE

Example 4

A problem may occur when using $BACK for a transfer between two nodes whose domains and organizations are different. To eliminate a problem with the use of $BACK when a transfer is being made between two nodes whose domains and organizations are different: configure the remote machine (using NMMGR; NM capability required), so that its network directory includes two entries:

   1)localnode.localdomain.localorganization, and
2) localnode.remotedomain.remoteorganization.

For example, if you were to issue a DSLINE from node A.LAB.CND to node B.SJ.CA, you would have to add the following entries to the network directory of node B.SJ.CA:

   A.LAB.CND
A.SJ.CA
Feedback to webmaster