× 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.



On 20 Dec 2012 07:53, David Gibbs wrote:

I'm having a bit of a brain cramp ... the CHGPF command has a
parameter WAITTIME [<ed: WAITFILE, per subject]...
most of the parameter values make sense, but the special value
*CLS doesn't.

*CLS
The default wait time specified in the class description is used
as the wait time for the file resources that are allocated.

Where is the class description for a file (physical or logical)
defined for the file ... and where do you define class descriptions?


As already described by Rob in another reply... However the "default wait time" that is established from the *CLS object for the initiation\creation of a job was eventually extended with the DFTWAIT() parameter of the CHGJOB CL command, to enable the adjustment of that attribute specific to a job [rather than all jobs under the WM using that Class]. AFaIK the specification of WAITFILE(*CLS), the "Maximum file wait time" on either the OVRDBF or the CRTxF or CHGxF uses the Default Wait Time value from the job, not from the actual Class object [type *CLS]; i.e. the help text should probably be more clear that the *CLS refers to the Default Wait for the job.

Note: very important to understand that this WAITFILE parameter applies to "open" requests; i.e. many will incorrectly refer to this parameter when some other non-open operation against a *FILE object has timed out, to infer how long that non-open operation should have waited.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.