RE: REXX here we go

[David FOXWELL <David.FOXWELL@xxxxxxxxx>]

That works, thanks. SET OPTION *NONE didn't.

Now, after all that I think I'd better test in my clp to see if the REXX procedure finished without any errors. Looked all over and can't find anything to test. Tried submitting a CLP to see if there was anything in the log. How do I test that RC = 0 back in my CLP.

-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de rob@xxxxxxxxx
Envoyé : lundi 21 avril 2008 17:01
À : Midrange Systems Technical Discussion
Objet : Re: REXX here we go

with nc

INSERT INTO ROB.BUBBA SELECT LOC FROM rob.aaakey WITH NC

2=NC (NONE)
    Specifies that commitment control is not used.  Uncommitted
    changes in other jobs can be seen.  If the SQL DROP COLLECTION
    statement is included in the program, *NONE or *NC must be used.
    If a relational database is specified on the RDB parameter and
    the relational database is on a system that is not on an
    iSeries, *NONE or *NC cannot be specified.


Just to bait Dave Odom, apparently "Read DBMS" don't allow you to specify no commitment control.  You just create the journals and journal the darn file - which is the right way.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Pete Helgren <Pete@xxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/21/2008 10:46 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc

Subject
Re: REXX here we go






David,

I am not a REXX programmer but the message may be eliminated by setting commitment control to *NONE  but I am unfamiliar with how to do that in REXX.

Pete


David FOXWELL wrote:
> Hi Joe,
>
> I'm just doing a DSPMSGD RANGE(SQL7008) MSGF(QSQLMSG). The code reason
is 3 which tells me the file isn't journalised, etc.
> -----Message d'origine-----
> De : midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Joe Pluta
> Envoyé : lundi 21 avril 2008 15:55
> À : Midrange Systems Technical Discussion Objet : Re: REXX here we go
>
> David FOXWELL wrote:
>
> > I probably should never have read Joe's introduction to REXX, as it's
been there longer than me and I've got by up till now without it. But I did and so now come the problems.
> > What's wrong with my first ever REXX procedure ? :
> >
> >
> > ADDRESS EXECSQL,
> >
> > "EXECSQL",
> >
> > " INSERT INTO QTEMP/ADHRBT ",
> >
> > " SELECT ADHRBT.* FROM ADHRBT JOIN PAFMT00 ON PA0COP =RRDTID ",
> >
> > " AND PA0TYP = 'INITIA' ORDER BY SUBSTR(PA0LIB, 68, 4)"
> >
> > IF RC < 0 THEN SAY SQLCODE
> >
> >
> >
> >
> >
> > I was getting SQLCODE -206 so I put up double quotes, now  I'm
> > getting
SQLCODE -7008.
> > Have checked the corresponding SQL0206 and SQL7008 messages.
> It sounds like you're getting there, David.  You fixed the -206 error,
now you're trying to figure out the -7008 error.  What's the second-level text for the SQL7008 error?
> Joe
> --
> 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.