RE: Do I have to recreate the SQLPKG, and why? -- MIDRANGE-L

If it does create the object, then why am I having to recreate the
SQLPKG?
And as far as the help goes...

Package help: Specifies the qualified name of the SQL package created on
the relational database specified on the RDB parameter of this command.
-- This implies that the package is already created.

Package *OBJLIB help:  The package is created in the library with the
same name as the library specified on the OBJ parameter.
-- This could imply that the command is creating the package (with the
'is' instead of 'was').  It could also be a poorly worded reference to
an object already created.

I just tested it.  While specifying the SQLPKG and RDB parameters, the
SQLPKG did not create with the execution of the CRTSQLRPGI command.
Again, maybe I'm missing a parameter, but so far I can't get the SQLPKG
to create when I create the module.   ...And as I say that, I realize
I'm creating a module.  Checked the help, and yep, there it is:

When OBJTYPE(*MODULE) is specified, an SQL package is not created and
you must issue the CRTSQLPKG command    
after the CRTPGM or CRTSRVPGM command has created the program.


Looks like I'll have to explore the Turnover way of doing this.

Thanks again for the help.
Kurt
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Phippard
Sent: Wednesday, February 02, 2005 3:38 PM
To: Midrange Systems Technical Discussion
Subject: RE: Do I have to recreate the SQLPKG, and why?

The help for those parameters certainly says that it creates a package.

You cannot do MOVOBJ or CRTDUPOBJ on the *SQLPKG object type so that
makes it pretty difficult to do any kind of CM on the object itself.
Also, since the *SQLPKG is always tied to a specific program, it is
easier to create it as a by-product of creating the program, either as
part of the CRT command or by linking the CRTSQLPKG command.

Mark


midrange-l-bounces@xxxxxxxxxxxx wrote on 02/02/2005 04:12:41 PM:

> I forgot to mention that I did specify the RDB parameter.
> I didn't see any documentation anywhere saying the SQLPKG would be 
> recompiled (but I would love for it to do so).
> 
> Thanks for the info about Turnover.  Didn't know it would remember a 
> post-command.  Didn't know it was object specific.  As it is I wish 
> Turnover allowed for the SQLPKG object type.  (When I emailed it as a 
> suggestion I never got a response).
> 
> Kurt
> 
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Phippard
> Sent: Wednesday, February 02, 2005 3:02 PM
> To: Midrange Systems Technical Discussion
> Subject: RE: Do I have to recreate the SQLPKG, and why?
> 
> I think you need to specify the RDB() parm as well.  Basically, the 
> parms that are on CRTSQLPKG also exist on the CRTSQLRPGI command.  If 
> you specify them the package will be created as part of the compile 
> process.
> 
> At least that is my understanding.
> 
> Mark
> 
> 
> midrange-l-bounces@xxxxxxxxxxxx wrote on 02/02/2005 03:49:46 PM:
> 
> > If this is true then I don't know the parm.
> > The only package relevant parameter I'm aware of that I'm using is:
> > SQLPKG *OBJ/*OBJLIB
> > 
> > Kurt
> > 
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx 
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Phippard
> > Sent: Wednesday, February 02, 2005 2:01 PM
> > To: Midrange Systems Technical Discussion
> > Subject: Re: Do I have to recreate the SQLPKG, and why?
> > 
> > I thought that you just typically used the relevant parms on the 
> > CRTSQLRPGI command to create the package, then the package would be 
> > recreated as part of the recompile.
> > 
> > Mark
> > 
> > 
> > midrange-l-bounces@xxxxxxxxxxxx wrote on 02/02/2005 02:43:46 PM:
> > 
> > > A workaround might be to have Turnover do a "Post Run" command to 
> > > create
> > 
> > > the package.
> > > 
> > > Rob Berendt
> > > --
> > > Group Dekko Services, LLC
> > > Dept 01.073
> > > PO Box 2000
> > > Dock 108
> > > 6928N 400E
> > > Kendallville, IN 46755
> > > http://www.dekko.com
> > > 
> > > 
> > > 
> > > 
> > > 
> > > "Kurt Anderson" <kjanderson@xxxxxxxxxxxxx> Sent by: 
> > > midrange-l-bounces+rob=dekko.com@xxxxxxxxxxxx
> > > 02/02/2005 01:50 PM
> > > Please respond to
> > > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > > 
> > > 
> > > To
> > > "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> 
> > > cc
> > > 
> > > Subject
> > > Do I have to recreate the SQLPKG, and why?
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > I have a SQLRPG program that has to access files created by a 
> > > software
> > 
> > > vendor which reside on a separate box.  We do have DDMs for those 
> > > files, but not with a key I need.  So I did a little research and 
> > > found that I could create a SQL Package which would allow me to 
> > > perform embedded SQL statements across systems.
> > > 
> > > >From what I've found, I need to have the SQLPKG reside on the 
> > > >system my
> > > program is using SQL to get to.  It seems that I must recreate the

> > > SQLPKG any time the object that references it is recompiled.  This

> > > wasn't so bad originally, but as time goes on, if any of our 
> > > database files change that this program uses, Turnover (our change

> > > management
> > > software) will recompile the program, but the SQLPKG remains as it
> > was.
> > > When this happens, and someone calls the program, they get a 
> > > data-decimal error.  Once I recreate the SQLPKG the error goes
away.
> > > 
> > > Is there a compile parameter I can specify that would prevent this

> > > error from occurring?
> > > Why is this error occurring?  (Ok, I understand that a numeric 
> > > field
> 
> > > has non-numeric data in it... but what is causing that?)
> > > 
> > > Thanks,
> > > 
> > > Kurt Anderson
> > > Application Developer
> > > Highsmith Inc.
> > > W5527 State Road 106, P.O. Box 800 Fort Atkinson, WI 53538-0800 
> > > TEL (920) 563-9571  FAX (920) 563-7395 EMAIL 
> > > kjanderson@xxxxxxxxxxxxx
> > 
> > 
> >
______________________________________________________________________
> > __
> > _____
> > Scanned for SoftLanding Systems, Inc. by IBM Email Security
Management
> 
> > Services powered by MessageLabs.
> >
______________________________________________________________________
> > __
> > _____
> > --
> > 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.
> > 
> > 
> > 
>
________________________________________________________________________
> _____
> > Scanned for SoftLanding Systems, Inc. by IBM Email Security
Management
> 
> > Services powered by MessageLabs.
> > 
>
________________________________________________________________________
> _____
> 
> 
>
________________________________________________________________________
> _____
> Scanned for SoftLanding Systems, Inc. by IBM Email Security Management
> Services powered by MessageLabs. 
>
________________________________________________________________________
> _____
> --
> 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.
> 
> 
> 
________________________________________________________________________
_____
> Scanned for SoftLanding Systems, Inc. by IBM Email Security Management

> Services powered by MessageLabs. 
> 
________________________________________________________________________
_____


________________________________________________________________________
_____
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management
Services powered by MessageLabs. 
________________________________________________________________________
_____
-- 
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.