HP3000-L Archives

June 2003, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Chip Dorman <[log in to unmask]>
Reply To:
Chip Dorman <[log in to unmask]>
Date:
Fri, 20 Jun 2003 10:09:07 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines)
Hi y'all,

I believe this is more a curiosity than a problem.

We have a job executing a command file.  The command file has two parms
both intended to hold HFS file names.  The first parm is a file mask and
the second parm is a fully qualified name.

What we are seeing is that in the job's STDLIST, the fully qualified file
name is not printing in the STDLIST.


This is the line from the job file.

!  rennext "/!hpaccount/!srcgrp/GLA20161@","/!hpaccount/!srcgrp/GLA20161"


This is the line from the job's STDLIST.  (I placed a couple of echo
statements to verify the parms, "mask" and "target".)

:  rennext "/!hpaccount/!srcgrp/GLA20161@","/!hpaccount/!srcgrp         "
mask /CHIP/JBS/GLA20161@
target /CHIP/JBS/GLA20161


Since the parms are passed intact, there is no harm being done.  This
seems to be an issue with parser confusing a HFS file name with a
file's lockword and that is all.  Right?


TIA,
Chip Dorman
Kennametal, Inc

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2