I think you're ok; the missing post-/ characters in $stdlist seems to be an
output-only side-effect of avoiding lockword display, left over from MPE2
and left in for backward compatibility, just in case somebody somewhere's
relying on this feature.

> -----Original Message-----
> From: Chip Dorman [mailto:[log in to unmask]]
> Sent: Friday, June 20, 2003 8:09 AM
> To: [log in to unmask]
> Subject: HFS names stdlist and lockwords
>
>
> 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 *
>

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