I note that if the size of the STORE to DISC file grows past 4GB
then STORE creates additional HFS files in the form FILENAME.#
where # is a sequence number starting at 2.

>                     A disk file can also be specified with a file
>                     equation for storefile. An example of such a
>                     file equation would be:
>
>                       FILE MYDISC=DISCBACK.DAILY.BACKUP;DEV=DISC
>
>                     Note that DEV=DISC must be specified for STORE
>                     to recover files from disk backups.  All other
>                     information in the file equation will be ignored
>                     by STORE. STORE creates a binary, fixed record
>                     file containing the backup data.  This
>                     disk file can be restored using the same file
>                     equation for RESTORE.
>
>                     By default, STORE creates the disk file with a
>                     4Gig limit.  If the data being stored exceeds
>                     this, or an existing file with a smaller limit
>                     is specified for the backup, then STORE will
>                     create and write to additional disk files.  It
>                     will append the "reel" number to the disk file
>                     name originally specified.  For example, if the
>                     backup disk file specified was
>                     /SYS/BACKUPS/DAILY, and STORE ran out of room,
>                     it would create /SYS/BACKUPS/DAILY.2,
>                     /SYS/BACKUPS/DAILY.3, and so on.  The additional
>                     files are HFS-named files.

This means that an STD (I just love that initialism!) store set
actually consists of the HFS files /ACCT/GROUP/FILENAME((.([2-9]|[1-
9][0-9]+))?)? all of which I have to move to the repository.  Now,
my backup job file is a MPE file and uses MPE file naming
conventions throughout.  What I want to do is to parse the STORE
filename descriptor (passed as a parameter via a system variable)
and convert it into its HFS equivalent so that I can then do this:

XEQ LS.HPBIN.SYS "-lpR <MPE filename in HFS form>*"

and this:

FTP
OPEN AAA.BBB.CCC.DDD
USER ANONYMOUS
BINARY
PROMPT
MPUT <MPE filename in HFS form>((.([2-9]|[1-9][0-9]+))?)?
QUIT

So, is there a readily available means to transform an MPE file
name into its HFS equivalent or do I have to write a parsing
routine myself?

Regards,
Jim

--
     *** e-mail is not a secure channel ***
mailto:byrnejb.<token>@harte-lyne.ca
James B. Byrne                Harte & Lyne Limited
vox: +1 905 561 1241          9 Brockley Drive
fax: +1 905 561 0757          Hamilton, Ontario
<token> = hal                 Canada L8E 3C3

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