Just today I restored a V5R2 job schedule object onto a V5R4 box as part of
an upgrade.
I've never had a problem restoring them between many different variations
You'll find that renaming it is an issue though - the RNMOBJ command does
not support *JOBSCD objects.
I do always save them to a save file but have never had reason to restore
from the backup.
Regards
Evan Harris
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Saturday, 13 December 2008 5:27 p.m.
To: Midrange Systems Technical Discussion
Subject: RE: V5R2 to V5R4 Upgrade and queues
Another option is to use the job scheduler api's on the existing release to
read them all and output that to a file. Then some program on the 'new'
system can read that file and ADDJOBSCDE them all back in.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
RE: V5R2 to V5R4 Upgrade and queues
Frances Denoncourt
to:
Midrange Systems Technical Discussion
12/12/2008 01:14 PM
Sent by:
midrange-l-bounces@xxxxxxxxxxxx
Please respond to Midrange Systems Technical Discussion
Rob,
I'll give it a try.
thanks,
Fran Denoncourt
Sr. Programmer/Analyst
Pinal County Treasurer's Office
Florence, AZ 85232
(520) 866-6404
Frances.Denoncourt@xxxxxxxxxxxxxxxxx
Receipt of this message does not grant you permission to send me
Unsolicited Commercial Email
<rob@xxxxxxxxx> 12/12/2008 10:44 AM >>>
Well, try this:
WRKOBJ OBJ(*ALL) OBJTYPE(*JOBSCD)
Rename the one on the 'new' box.
Restore the one from the old box.
Try WRKJOBSCDE, etc.
If it tells you to FOAD then rename the restored one and rename the one
that came with the new box back to the real name.
Rob Berendt
midrange.com
