Re: Another V6.1 issue: CPF3837 -- MIDRANGE-L

This points out a recommendation that is often missed when sites are either new to the platform, or rarely upgrade.
It is never recommended to run any user jobs with system profiles. Your *allobj "vanishing" is because on a new release, all the system profiles are restored with the new release media. Same with system definitions of subsystems, commands, job descriptions, printer files, etc in IBM's "Q" libraries. There are exceptions, ways to control what gets replaced, ways to reapply changes, etc but absent those efforts and the knowledge of what really happens in an upgrade, it is not a good thing to run your jobs with an IBM profile.
If you have vendor products running jobs under altered system profiles or objects-tell them to stop it! No release upgrade should be hostage to a vendors sloppy code.
(btw-i do mean "user" jobs, and not the multitude of jobs that need to execute with system profiles - and if you are altering those - you better understand the consequences)
Jim Franz
----- Original Message ----- From: "Robert Ostrowski" <Bob.Ostrowski@xxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Sunday, May 16, 2010 8:55 AM
Subject: RE: Another V6.1 issue: CPF3837

That's the way it's been ever since I started working here. Being that
I'm the only RPG programmer (aside from our CIO), and nobody else in the
company has access to a command line, I think we're OK. I admit I'm no
AS/400, iSeries, or IBM I system guru and I don't know all of the in's
and out's of security and all the underlying things going on in the
bowels of the system like many of the people on this list. Our
overnight submits a job to batch, and that's how it runs (with QPGMR).

I post questions on this list to learn new things and possibly the
correct and safest way to do them. I don't post my questions to be
asked "Why am I doing it that way?". It would be nice to see "You can
do it that way, but it isn't the best. Maybe you should do it this
way...".

I haven't spent my whole life on the IBM system. Probably 1/5 of the
time of many of the people on this list. Being that I am the only AS400
programmer here, this list is one of the few places I have to fall back
on for advice.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Massiello
Sent: Saturday, May 15, 2010 9:46 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Another V6.1 issue: CPF3837

All your problems have just started. QPGMR with ALLOBJ? Why do you run
everything from QPGMR?

Pete Massiello
iTech Solutions
http://www.itechsol.com

Add iTech Solutions on Facebook:
http://www.facebook.com/group.php?gid=126431824120
Add iTech Solutions on LinkedIn:
http://www.linkedin.com/groups?gid=2206093

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Robert Ostrowski
Sent: Saturday, May 15, 2010 3:33 PM
To: Midrange Systems Technical Discussion
Subject: RE: Another V6.1 issue: CPF3837

Problem solved. Apparently the *ALLOBJ authority on the QPGMR batch
user profile vanished into thin air when we moved everything to the new
box. I added it, and all my problems went away.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Robert Ostrowski
Sent: Saturday, May 15, 2010 6:45 AM
To: Midrange Systems Technical Discussion
Subject: Another V6.1 issue: CPF3837

Since upgrading to V6.1, in our overnight save we keep encountering
CPF3837 in testing the backup. I added a MONMSG MSG(CPF3837) for it,
but it still comes up. Do I need to do more than just add the MONMSG?
I would love to avoid getting up at 2:00 AM to type "I" to ignore the
message every night!!
--
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.