|
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
midrange-l-request@xxxxxxxxxxxx
Sent: Friday, July 20, 2007 1:00 PM
To: midrange-l@xxxxxxxxxxxx
Subject: MIDRANGE-L Digest, Vol 6, Issue 1396
Send MIDRANGE-L mailing list submissions to
midrange-l@xxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/midrange-l
or, via email, send a message with subject or body 'help' to
midrange-l-request@xxxxxxxxxxxx
You can reach the person managing the list at
midrange-l-owner@xxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of MIDRANGE-L digest..."
*** NOTE: When replying to this digest message, PLEASE remove all text
unrelated to your reply and change the subject line so it is
meaningful.
Today's Topics:
1. SQL and QTEMP (Jerry Adams)
2. RE: SQL and QTEMP (Elvis Budimlic)
3. RE: It only happen on a Friday (John Candidi)
4. RE: SQL and QTEMP (Wilt, Charles)
5. Re: Need Ideas for Batch Job Submission (Scott Klement)
----------------------------------------------------------------------
message: 1
date: Fri, 20 Jul 2007 11:38:36 -0600
from: Jerry Adams <jerry@xxxxxxxxxxxxxxx>
subject: SQL and QTEMP
Just started using SQL's DDL, as opposed to DDS, to create files.
Done about a dozen so far (new and re-vamped) with only cosmetic
problems (oversized fingers on undersized keyboard).
But today I tried creating a file in QTEMP from DDL. The procedure
(CL) issued a SQL9010 error (RUNSQLSTM command failed). Higher up in
the joblog is CPD32B0 (Constraint is not valid):
Cause . . . . . : Constraint *N cannot be added for file ALPBSEL in
library
QTEMP for TYPE value *N. For a referential constraint (TYPE
*REFCST), the
parent file *N in library *N has a delete rule of *N and update rule
of *N.
The constraint was not added because of errors. The reason code is
15.
15 - The file cannot be in the QTEMP library
The DDL is pretty simple:
CREATE TABLE ALPBSEL (
ABLOCAL1 CHAR(5) CCSID 37 NOT NULL ,
ABLOCAL2 CHAR(5) CCSID 37 NOT NULL ,
ABLOCAL3 CHAR(5) CCSID 37 NOT NULL ,
PRIMARY KEY( ABLOCAL3 ,
ABLOCAL2 , ABLOCAL1 ) )
;
LABEL ON TABLE ALPBSEL
IS 'Alabama Price Book Selections' ;
LABEL ON COLUMN ALPBSEL
( ABLOCAL1 IS 'First Local Code' ,
ABLOCAL2 IS 'Second Local Code' ,
ABLOCAL3 IS 'Third Local Code' ) ;
LABEL ON COLUMN ALPBSEL
( ABLOCAL1 TEXT IS 'First local code selected' ,
ABLOCAL2 TEXT IS 'Second local code selected' ,
ABLOCAL3 TEXT IS 'Third local code selected' ) ;
I used the following to try to create it:
RUNSQLSTM SRCFILE(ADSOE200/QSQLSRC) SRCMBR(ALPBSEL) +
COMMIT(*NONE) DFTRDBCOL(QTEMP)
Does SQL just refuse to play in the QTEMP sandbox or did I miss a
parameter in the DDL or RUNSQLSTM?
--
* Jerry C. Adams
*IBM System i Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
615.995.7024
fax
615.995.1201
jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>
------------------------------
message: 2
date: Fri, 20 Jul 2007 11:51:55 -0500
from: "Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx>
subject: RE: SQL and QTEMP
There are some things you can use QTEMP for but as a general rule you
should avoid it. Its transient nature is not part of standard SQL.
That said I still use QTEMP for work files and such, but these are
vanilla files (i.e. no primary keys, referential constraints etc.).
Elvis
Celebrating 10-Years of SQL Performance Excellence
http://centerfieldtechnology.com/training.asp
-----Original Message-----
Subject: SQL and QTEMP
Just started using SQL's DDL, as opposed to DDS, to create files.
Done about a dozen so far (new and re-vamped) with only cosmetic
problems (oversized fingers on undersized keyboard).
But today I tried creating a file in QTEMP from DDL. The
procedure (CL)
issued a SQL9010 error (RUNSQLSTM command failed). Higher up in the
joblog is CPD32B0 (Constraint is not valid):
Cause . . . . . : Constraint *N cannot be added for file ALPBSEL in
library
QTEMP for TYPE value *N. For a referential constraint (TYPE
*REFCST),
the
parent file *N in library *N has a delete rule of *N and
update rule
of *N.
The constraint was not added because of errors. The reason
code is 15.
15 - The file cannot be in the QTEMP library
The DDL is pretty simple:
CREATE TABLE ALPBSEL (
ABLOCAL1 CHAR(5) CCSID 37 NOT NULL ,
ABLOCAL2 CHAR(5) CCSID 37 NOT NULL ,
ABLOCAL3 CHAR(5) CCSID 37 NOT NULL ,
PRIMARY KEY( ABLOCAL3 ,
ABLOCAL2 , ABLOCAL1 ) )
;
LABEL ON TABLE ALPBSEL
IS 'Alabama Price Book Selections' ;
LABEL ON COLUMN ALPBSEL
( ABLOCAL1 IS 'First Local Code' ,
ABLOCAL2 IS 'Second Local Code' ,
ABLOCAL3 IS 'Third Local Code' ) ;
LABEL ON COLUMN ALPBSEL
( ABLOCAL1 TEXT IS 'First local code selected' ,
ABLOCAL2 TEXT IS 'Second local code selected' ,
ABLOCAL3 TEXT IS 'Third local code selected' ) ;
I used the following to try to create it:
RUNSQLSTM SRCFILE(ADSOE200/QSQLSRC) SRCMBR(ALPBSEL) +
COMMIT(*NONE) DFTRDBCOL(QTEMP)
Does SQL just refuse to play in the QTEMP sandbox or did I miss a
parameter in the DDL or RUNSQLSTM?
--
* Jerry C. Adams
------------------------------
message: 3
date: Fri, 20 Jul 2007 13:02:16 -0400
from: "John Candidi" <jacandidi@xxxxxxxxxxxxxxxxxxxx>
subject: RE: It only happen on a Friday
I had a user sign on and select option 10 to signoff. Did
this 4 or 5 times
before calling me and telling me she keeps getting kicked off
the system. I
went over and saw what she was doing and she denied even
after I stood there
and watched her do it a few more times. Oh, it was Monday
morning, maybe
that made a difference
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Denis Robitaille
Sent: Friday, July 20, 2007 10:00 AM
To: MIDRANGE-L@xxxxxxxxxxxx
Subject: It only happen on a friday
Hello all,
Users will never stop surprising me.
This morning, one of our tech support told us the following (he had to
share this):
A user was trying to logon on someone else's work station.
After typing
her id and password, a window popped up that said :
"Wrong password, Please type your password again .. Remember the
password is Case-Sensitive"
Well, after reading this, she types "Case-Sensitive" as the password
and tried to log in!!!
--
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.
------------------------------
message: 4
date: Fri, 20 Jul 2007 13:05:47 -0400
from: "Wilt, Charles" <WiltC@xxxxxxxxxx>
subject: RE: SQL and QTEMP
Jerry,
While SQL doesn't seem to want to create a table with a
primary key in QTEMP.
You can create a table without a primary key and add a unique index.
Or you can create the table with a primary key in another
library and CRTDUPOBJ to QTEMP.
HTH,
Charles
-----Original Message-----ALPBSEL in
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry Adams
Sent: Friday, July 20, 2007 1:39 PM
To: Midrange-L
Subject: SQL and QTEMP
Just started using SQL's DDL, as opposed to DDS, to create
files. Done about a dozen so far (new and re-vamped) with
only cosmetic problems (oversized fingers on undersized keyboard).
But today I tried creating a file in QTEMP from DDL. The
procedure (CL) issued a SQL9010 error (RUNSQLSTM command
failed). Higher up in the joblog is CPD32B0 (Constraint is
not valid):
Cause . . . . . : Constraint *N cannot be added for file
library
QTEMP for TYPE value *N. For a referential constraint (TYPE
*REFCST), the
parent file *N in library *N has a delete rule of *N and
update rule of *N.
The constraint was not added because of errors. The reason
code is 15.
15 - The file cannot be in the QTEMP library
The DDL is pretty simple:
CREATE TABLE ALPBSEL (
ABLOCAL1 CHAR(5) CCSID 37 NOT NULL ,
ABLOCAL2 CHAR(5) CCSID 37 NOT NULL ,
ABLOCAL3 CHAR(5) CCSID 37 NOT NULL ,
PRIMARY KEY( ABLOCAL3 ,
ABLOCAL2 , ABLOCAL1 ) )
;
LABEL ON TABLE ALPBSEL
IS 'Alabama Price Book Selections' ;
LABEL ON COLUMN ALPBSEL
( ABLOCAL1 IS 'First Local Code' ,
ABLOCAL2 IS 'Second Local Code' ,
ABLOCAL3 IS 'Third Local Code' ) ;
LABEL ON COLUMN ALPBSEL
( ABLOCAL1 TEXT IS 'First local code selected' ,
ABLOCAL2 TEXT IS 'Second local code selected' ,
ABLOCAL3 TEXT IS 'Third local code selected' ) ;
I used the following to try to create it:
RUNSQLSTM SRCFILE(ADSOE200/QSQLSRC) SRCMBR(ALPBSEL) +
COMMIT(*NONE) DFTRDBCOL(QTEMP)
Does SQL just refuse to play in the QTEMP sandbox or did I
miss a parameter in the DDL or RUNSQLSTM?
--
* Jerry C. Adams
*IBM System i Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
615.995.7024
fax
615.995.1201
jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>
--
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 e-mail transmission contains information that is
intended to be confidential and privileged. If you receive
this e-mail and you are not a named addressee you are hereby
notified that you are not authorized to read, print, retain,
copy or disseminate this communication without the consent of
the sender and that doing so is prohibited and may be
unlawful. Please reply to the message immediately by
informing the sender that the message was misdirected. After
replying, please delete and otherwise erase it and any
attachments from your computer system. Your assistance in
correcting this error is appreciated.
------------------------------
message: 5
date: Fri, 20 Jul 2007 12:07:17 -0500
from: Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>
subject: Re: Need Ideas for Batch Job Submission
The system comes with an API called setitimer() that will send you a
signal on a given interval. For example, you could tell it
to send you
a signal every 15 minutes.
You could write a program (albeit, not in CL) that would start this
interval timer and handle the signals. This would cause a procedure
(RPG subprocedure, COBOL procedure, C function) that's called
every 15
minutes. That procedure could then run whatever task is desired.
IMHO, this would be easier than re-calculating the RSMTIME to account
for how long some command ran.
Wilt, Charles wrote:
Not sure what you mean Scott.
Can you elaborate?
Charles
------------------------------
--
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) digest 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.
End of MIDRANGE-L Digest, Vol 6, Issue 1396
*******************************************
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
