RE: V5R2 to V5R4 Upgrade and queues -- MIDRANGE-L

Thanks again, Rob.
We didn't have too many jobs in our queues, but other departments did and expressed concern.
Wish I had asked these questions earlier, but having out sourced the whole thing we [programmers] thought we were more or less working with people who understood our needs. Not entirely what happened.
But, we seem to be up and running with a few wrinkles to iron out - so far. Still checking things out.

BTW our email server just had issues and I have no idea why I'm getting my email formatted this way. Groupwise has been a thorn in our sides for some time.

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 9:32 PM >>>

And be careful with this stuff. Sometimes conversions (sort of like file layouts) can occur from release to release. In the olden days I used to have to save off subsystem QBATCH and restore it after each upgrade or I lost all of my job queue entries. However after one release you no longer had to do that "BUT" if your subsystem description was created prior to release xyz then it would not do it. Cure? Use every known api to retrieve subsystem information to a file. DLTSBSD QBATCH CRTSBSD QBATCH Use the information gleaned off of the api's to ADDJOBQE, etc. (programmatically) Oh, and I had several hundred job queue entries. Hence my second recommendation to delve into the APIs for the OP. 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 John McKee to: midrange-l 12/12/2008 02:38 PM Sent by: midrange-l-bounces@xxxxxxxxxxxx Please respond to Midrange Systems Technical Discussion That command displayed interesting information on our system. When I started here, we had an E70, running (I thing v3r1). Conversion to RISC and three upgrades later, creation date and time are: 11/14/92 03:40:38 So, I take it that the object itself was moved from platform to platform. I have no idea if the content also moved in the early days (before my time). Just interesting that the creation date is unchanged despite hardware, operating syatem, and serial number changes. Restoring an object means restoring an object, I suppose. John McKee Quoting rob@xxxxxxxxx: > 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 > -- > Group Dekko Services, LLC > Dept 01.073 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com > > > > > > From: > "Frances Denoncourt" > To: > "'Midrange Systems Technical Discussion'" > Date: > 12/12/2008 10:27 AM > Subject: > RE: V5R2 to V5R4 Upgrade and queues > Sent by: > midrange-l-bounces@xxxxxxxxxxxx > > > > Evan, > Thanks for the response. > > Yes, we are moving onto a new box as well. > Too bad about the job queue entries. We were hoping there was a work > around. > > How does it work for job scheduler entries: WRKJOBSCDE? > Do we lose them, too? > > The upgrade is tomorrow morning - Saturday. > Thanks again, > > > 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 > > >>>> "Evan Harris" 12/11/2008 5:06 PM >>> > Hi Fran > > If you're just doing an upgrade on the one box you shouldn't need to do > anything other than run the automatic upgrade process. > > If you are moving onto a new box via an unload/reload then you will lose > spool files and job queue entries. You can send the spool files across > afterwards if you want (presuming the box is still intact) using remote > outqeueues to transfer them. You can even upgrade the old box afterwards > and > then save and restore the old spool files if you want to see how this > feature works. As to Job queue entries, in this situation I think your out > of luck. > > You'll probably get a better answer if you describe the scenario in more > detail. > > Regards > Evan Harris > > > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Frances Denoncourt > Sent: Friday, 12 December 2008 12:38 p.m. > To: midrange-l@xxxxxxxxxxxx > Subject: V5R2 to V5R4 Upgrade and queues > > Is it possible to save/restore job queues and output queues when upgrading > from V5R2 to V5R4...I hear them talking about 'skip', so maybe we are > skipping V5R3. > > Just checked the archive - didn't see it. > > The memo to users for both V5R3 and V5R4 didn't talk about it either. > > Thanks, > > > > Fran Denoncourt > Sr. Programmer/Analyst > Pinal County Treasurer's Office > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.