RE: AS/400 Report Writers

[gmihajlo@xxxxxxxx]

Talking about the system value QQRYTIMLMT, rather than changing it, in many
cases it might be more beneficial if similar value is defined at the job level
by using command CHGQRYA (Change Query Attributes) and specifying appropriate
value for parameter QRYTIMLMT (Query Time Limit), which will affect only
specified job instead of whole system. I don't have original posting anymore and
cannot remember if this is applicable to that case because it is obviously not
convenient solution for queries running in batch jobs submitted from BPCS, but
might be useful even in some batch jobs providing you have at least some
(submitting) control over them, for example:
instead  of

SBMJOB CMD(CALL PGM(PGM123B))

where PGM123B is a RPG program which contains long running query, you would do

SBMJOB CMD(CALL PGM(PGM123C))

where PGM123C would be a new CL program which does something like:

PGM
CHGQRYA QRYTIMLMT(15)
CALL PGM(PGM123B)
SBMJOB
ENDPGM

Goran



If I may interject? There is indeed a QQRYTIMLMT system value on the AS/400.
It can be increased, or set to *NOMAX. There could be problems, though, if
(for instance) a user sets an SQL parameter so that too much data is
selected just before (let us say) backups are supposed to kick off. This
could cause serious operations problems. I would recommend that users be
trained, and sanctions set for those who abuse granted authorities too much
("one slip, shame on you; two slips, shame on me", so to speak).

I do have one question, with respect to BPCS: Does it normally use
journaling, with before-and-after images, and commitment control? I would
have thought it does, in which case many kinds of problems would be easier
to deal with. One could use the journals to roll production files back to a
particular point in time, or restore them, as well as mitigating problems
from device, or system, crashes. If the files tend to grow too quickly for a
daily backup routine, a new routine could be defined to backup the journals
more often.

Just thinking,
Richard Allan Stauch
System Engineer, EDS
*    (562) 809-4861 (Voice)
*    (562) 860-8506 (Fax)
*    richard.stauch@eds.com (E-mail)


-----Original Message-----
From: Chick Doe [mailto:Cdoe@barton-instruments.com]
Sent: Friday, May 05, 2000 7:42 AM
To: BPCS-L@midrange.com
Subject: RE: AS/400 Report Writers


george, here are a couple possibilities.

1. i believe that the as/400 has a system value called QQRYTIMLMT which set
the maximum time limit for queries. when a query is submitted the estimated
time that it will take to process is compared against this system value and
if the estimated time is greater, the query is not run. this time limit can
be increased.
2. as far as allowing users to run update queries from access, i believe
that you can configure the ODBC DSN as read only. if you constructed a read
only DSN and told the users to use that one, i don't think it would allow an
access update query to run.
[Snip]




+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---