Hello Les,
I have removed the PORT-9100 and indeed now I get the output on the print
er.
Also I tried this with both LPRXPSE and LPRXONE and both gave me output.
The
first in postscript and the second in plain text. The actual output doesn
't
differ all that much but the separation page is
Hello David,
1) remove the PORT=9100. Port 9100 is the HP socket printing protocol,
not
LPR/LPD. The two are not interoperable, and RSCS doesn't know squat about
the HP protocol (it'd sure be nice if RSCS got IPP support -- hint, hint)
I tried without PORT (therefore with the default 515)
Joe,
I usually put all IBM products on the 3 res packs provided.
I then put all the 3rd party products on there own packs and
then put USERS on another set of packs and LINUX on another set.
I like to keep them separate that way and also I provide separate sections
of the USER DIRECT also
I want to thank all of you for your input. It has been very benifical.
Joseph Di Pippo
Operating Systems Programmer III
FRIT Computing Services
Hardware Support
1-201-531-3820
Bill Munson william.mun...@bbh.com
Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
07/09/2009 08:38
Anyone on the list using CA's VM:Backup with HiDRO for Disaster
Recovery? I am curious how you addressed the requirement of creating a
userid called VMIMAGE which owns all the data in the shop. I am
concerned about the VMIMAGE user 'owning' the data. What exactly does
this mean and kind of
We have been using it for years (now only if the mirroring fails).
We use VMIMAGE (well, another userid) over the system volumes only.
Once those are restored, we have enough to bring up the system do the incrgen
and submit the restores to the HIDRO.
It's just full pack overlay minidisks in
At one of my shops we use HIDRO for daily / weekly backups
and take DDR full volume back ups for DR on a schedule
the shop is so small, with very little changes to system volumes, this is
feasible
after the DDR restores we bring up the system and use HIDRO backups to
bring needed IDs current
Dave,
Just like the 123 mdisk on the MAINT user id it is a FULLPACK minidisk
definition of all your dasd that you want HiDRo to backup.
MDISK 123 3390 END V3R001 MR
the 123 MDISK has to be in Maint so that DIRMAINT, VM:Secure, or
VM:Director can use it to run DIRECTXA
MDISK 202E
Hello!
Please ignore this message. It is being used to confirm that the list server
can see my messages, and the manager can complain if he so wishes.
--
Gregg C Levine hansolofal...@worldnet.att.net
The Force will be with you always. Obi-Wan Kenobi
