Does ISQL works for remote UDB(DB2) on Linux ?

[Arye Shemer]

Hello Forumers,
Can I use the CICS transaction ISQL for remote UDB(DB2) database on Linux ?

Thanks,

Arye, Shemer.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to list...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

[Frank Swarbrick]

Are you refering to the VSE DB2 CICS transaction ISQL? If so, then yes you can.
--

Frank Swarbrick
Applications Architect - Mainframe Applications Development
FirstBank Data Corporation - Lakewood, CO USA
P: 303-235-1403

On 1/3/2010 at 10:06 AM, in message
<LISTSERV%20100103110...@BAMA.UA.EDU>, Arye Shemer

>>>

The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you.

[Arye Shemer]

Thank you Frank,

Yes, I am refering to VSE DB2 CICS ISQL transaction.

It arose another question, in the isntallation process of the package
for ISQL, I noticed
that one of the element is a stored procedure.
If I understand correctly stored procedures should be run in the
machine where the
database is running.
If my understanding is correct,
My question is: what language this stored procedure is written with
and how it can be run
on UDB (DB2) server which run on Windows?

Thanks for clarifying this for me.

Arye Shemer.

[Rich Smrcina]

If you would have mentioned VSE ISQL in the first place... not knowing
whether there's a z/OS equivalent.

Yes, as Frank indicated, works great, use it all the time. Packages
will need to be bound to the remote database.

Not sure what you mean by stored procedure elements... as far as I know,
they are not required for ISQL to function, just bind the ISQL packages
to the remote database.

On 01/05/2010 07:59 AM, Arye Shemer wrote:
> Thank you Frank,
>
> Yes, I am refering to VSE DB2 CICS ISQL transaction.
>
> It arose another question, in the isntallation process of the package
> for ISQL, I noticed
> that one of the element is a stored procedure.
> If I understand correctly stored procedures should be run in the
> machine where the
> database is running.
> If my understanding is correct,
> My question is: what language this stored procedure is written with
> and how it can be run
> on UDB (DB2) server which run on Windows?
>
> Thanks for clarifying this for me.
>
> Arye Shemer.
>
> On Mon, Jan 4, 2010 at 7:43 PM, Frank Swarbrick
> <frank.s...@efirstbank.com> wrote:
>
>

--
Rich Smrcina
Phone: 414-491-6001
http://www.linkedin.com/in/richsmrcina

Catch the WAVV! http://www.wavv.org
WAVV 2010 - Apr 9-13, 2010 Covington, KY

[Frank Swarbrick]

ISQL doesn't require any stored procedures that I know of. What it does require is that you bind the ISQL "package" to the remote server. To do this you have to use the DBSU utility (ARIDBS), and to use that you have to bind the DBSU package to the remote server. So there's two steps:

This one binds the package so that ARIDBS (DBSU) can be used.
// JOB DB2PPA
// SETPARM DBPROG='SQLDBA.ARIDSQL'
// SETPARM DBNAME=<name of remote database>
// SETPARM DBUSER=<name of remote database user>
// SETPARM DBPSWD=<password of remote database user>
// EXEC PGM=ARIPRPA,SIZE=AUTO, X
PARM='PREP=&DBPROG,USERID=&DBUSER/&DBPSWD,DB=&DBNAME,', X
PARM='BLOCK,ISOL(CS),PR,NOPU,CTOKEN(NO),ERROR'
* $$ SLI MEM=ARIDSQLP.A,S=PRD2.DB2750
/*
/&

// JOB ARIDBS
// EXEC ARIDBS,SIZE=AUTO
CONNECT <remote user name> IDENTIFIED BY <remote user password> TO <remote database name>;
RELOAD PROGRAM (SQLDBA.ARIISQL) REPLACE KEEP INFILE(SYSIPT BLKSZ(80)
PDEV(DASD));
READ MEMBER ARIISQLM
COMMIT WORK;
/*

--

Frank Swarbrick
Applications Architect - Mainframe Applications Development
FirstBank Data Corporation - Lakewood, CO USA
P: 303-235-1403

On 1/5/2010 at 6:59 AM, in message
<a642e5981001050559p1b1...@mail.gmail.com>, Arye Shemer

[Arye Shemer]

Thank you all,

It was very helpfull

Arye Shemer.

On Tue, Jan 5, 2010 at 7:02 PM, Frank Swarbrick