× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



>
> No clean up necessary as once the job ends, normally or not, the
> lock is released.
>

Ahh yes, and that's the difference.

In the case of which I speak I DO NOT want the original process to continue (yet) if the secondary process abends. In the POWERHA steps I use this for if it doesn't complete that means the iASP is not available and the rest of the startup job would go down in flames. I need it to wait.

So not arguing right or wrong here just pointing out that the two methods are different. One defaults to 'Go Ahead' and the other 'WAIT'. Rather like the difference between DOWHILE and DOUNTIL each has it's place.

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 3/8/2018 9:45 AM, Christopher Bipes wrote:
Dr. Franken,

While the data area works, I do not like to check for existence but for a lock. After submitting the job, have the submitter delay a certain amount of time, and then check for a lock on the data area. The first thing the submitted job does is an ALCOBJ OBJ((LIBRARY/DATAAREA *DATARA *EXCL))

Chris Bipes
Director of Information Services
CrossCheck, Inc.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DrFranken
Sent: Wednesday, March 07, 2018 11:41 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: System startup porgram and adopted authority

The points thus far have been good and accurate.

One thing not mentioned is that certain authorities are NOT adoptable.
As a consequence even owning the program by QSECOFR is not sufficient. A
common case I run into is the pieces that POWERHA requires to be
started. QPGMR can't do it and the needed authority cannot be adopted.

So I generally do a variation on the earlier suggestions in this thread
and with Jim's thinking try to box tight the use of higher authority. I
create a profile that has no password and no command line ability. I
grant authority to QPGMR to use that profile. In the startup job I
submit the program with the needed steps using the profile.

One thing I've done is for steps that need to be completed before the
startup job continues is to create a data are just before submitting the
second task. At the end of that task the data area is deleted. Meanwhile
the primary startup job loops waiting for the data area to disappear.

Clearly not the only way to do this but it has worked well.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.