ca.portal.admin

Re:[IDMS-L] Java/Websphere/CICS/IDMS transaction

Discussion created by ca.portal.admin on Jun 16, 2005
We have a customer that has developed an application that is for the most
part a Java/Websphere/DB2 application. However they need to retrieve some
information form an IDMS legacy system. They have set this application to
use a single user id even though there will be hundreds of users. The
transaction flow, as I understand it, is for Java to make a request to
Websphere who makes a request to CICS Transaction gateway to execute a
transaction on the legacy CICS to retrieve the information. What is
happening is that occasionally - they say once in about 500 transactions -
the information goes to the wrong end-user. Has anyone had any experience
with this scenario? Right now I'm going on the premise that since the CICS
transaction being executed is a ""tried and true"" legacy transaction that the
problem is not in IDMS or CICS. I'm going through Java/WebSphere manuals
like crazy to see how they control their connections but I thought I would
throw it out to the list to see if anyone has any ideas.



*************************
CONFIDENTIALITY STATEMSent:
This e-mail and any attachments are intended only for those to which it is
addressed and may contain information which is privileged, confidential and
prohibited from disclosure and unauthorized use under applicable law. If you
are not the intended recipient of this e-mail, you are hereby notified that
any use, dissemination, or copying of this e-mail or the information
contained in this e-mail is strictly prohibited by the sender. If you have
received this transmission in error, please return the material received to
the sender and delete all copies from your system.


*************************
CONFIDENTIALITY STATEMSent:
This e-mail and any attachments are intended only for those to which it is
addressed and may contain information which is privileged, confidential and
prohibited from disclosure and unauthorized use under applicable law. If you
are not the intended recipient of this e-mail, you are hereby notified that
any use, dissemination, or copying of this e-mail or the information
contained in this e-mail is strictly prohibited by the sender. If you have
received this transmission in error, please return the material received to
the sender and delete all copies from your system.

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
IDMS Abends in Local Mode Batch
"Hi,



I can see that 16.0 has changed the way that Local Mode jobs handle
abends for non zero IDMS error_status codes. Using the COPY IDMS
IDMS-STATUS module will force a ROLLBACK that now gives a DC329009
message and stops ABENDAID from taking control and giving us a nicely
formatted dump.



Is there a way to get back to the old method and not have IDMSTMGR
intercept? Will QO61579 fix this or do we need to change the batch
version of IDMS_STATUS?



We didn't have any abends in testing, are we weren't told, so we had not
seen this before implementation.



Thanks



Chris Wood

Alberta Department of Energy

CANADA

This communication is intended for the use of the recipient to which it is addressed, and may contain confidential, personal and or privileged information. Please contact us immediately if you are not the intended recipients of this communication, and do not copy, distribute, or take action relying on it. Any communication received in error, or subsequent reply, should be deleted or destroyed.

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Testing Version Number
"Hello - I'm sorry for the 2 packages you recieved earlier from me. Please
delete them. My emails went through a product we have that packages up
emails in some instances. I'm hoping this email will go directly to you.



I wanted to Thank Gary Cherlet and Tim Gortner for the suggestions. I gave
IDMSIN01 a try and it worked. One thing to note is the parms must all be
separate - I had originally put them all in 1 work record and the link
didn't work. So I separated them and it worked like a charm. If anyone is
interested in the code I used - I included it below. Thanks again for the
help!

01 IDMSIN01-PARM1-REC.
02 IDMSIN01-REQUEST-RPB PIC X(36).

01 IDMSIN01-PARM2-REC.
02 IDMSIN01-REQUEST-CODE PIC S9(08) COMP.
02 IDMSIN01-REQUEST-RETURN PIC S9(08) COMP.

01 IDMSIN01-PARM3-REC.
02 IDMSIN01-REQUEST-KEYWD PIC X(08).

01 IDMSIN01-PARM4-REC.
02 IDMSIN01-RETURNED-VALUE PIC X(32).


INITIALIZE (IDMSIN01-PARM1-REC).
INITIALIZE (IDMSIN01-PARM2-REC).
INITIALIZE (IDMSIN01-PARM3-REC).
INITIALIZE (IDMSIN01-PARM4-REC).

MOVE 2 TO IDMSIN01-REQUEST-CODE. <-- 2 IS THE CODE TO
GET PROFILE
MOVE 'TEST' TO IDMSIN01-REQUEST-KEYWD. <-- TEST IS TO GET THE
VERSION

LINK TO PROGRAM 'IDMSIN01' USING (IDMSIN01-PARM1-REC,
IDMSIN01-PARM2-REC,
IDMSIN01-PARM3-REC,
IDMSIN01-PARM4-REC).


Thanks
Ruth Kraber-Lendt
Child Welfare Information Systems (CWIS)
rkraber@dhs.state.ia.us
515-281-0376

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: SVC JCL
"First, do an SMP/E LIST of the load module with XREF in the target zone. For example,

SET BOUNDARY(IDMSTGT).
LIST LMOD(IGC176) XREF.

A LIST LMOD command shows you whether the load module is reentrant, and gives you things like ORDER, ENTRY and MODE statements. The XREF parameter also shows what object modules are included in the load module. The object modules should be included from DISTLOAD.

After running the LIST command for the load module, run another LIST for each object module. Run this list in both the target zone and the distribution zone. For example,

SET BOUNDARY(IDMSTGT).
LIST MOD(#SVCOPT,IDMSMSVC,GSISVCX,IDMSCMSO,IDMSMSVM).
SET BOUNDARY(IDMSDLB).
LIST MOD(#SVCOPT,IDMSMSVC,GSISVCX,IDMSCMSO,IDMSMSVM).

The object module LIST shows what apars are on the modules. (If you have FMID and RMID subentries but no UMID subentries, there are no apars.) If some of these apars are installed in the target zone but not installed in the distribution zone, then you need to either ACCEPT them (but ACCEPT only apars that are lower than the high apar of the next maintenance tape you will install) before running the link or else zap the load module after running the link.

Probably most sites have fewer object modules linked into their SVC load module than shown above, depending on what products have been installed.

There is an SVC load module in the APFLIB library. If you link an SVC load module outside of SMP/E, it should be the same size.

There should be source for #SVCOPT in the PPOPTION library. It should look similar to this:
#SVCOPT,
SVCNO=your-svc-number,
SVCXLEN=0, size could be increased for Tools install
ENVIRON=(MVS,VMCF), if CMS option is installed
ENVIRON=MVS, if CMS option is not installed
PSWMODE=EC, if CMS option is installed
LAP=YES, if CMS option is installed
DBUGCMS=YES, if CMS option is installed
MAXTCB=1, if CMS option is installed
VMBUFCT=10, if CMS option is installed
VMCFLOC=X'230', if CMS option is installed, where X'230' is
the low core hex address for program status word
VMCFCPU=NO, if CMS option is installed
CVKEY=, primary protect key
SMF=YES
END

This JCL seemed to work.

//ASSEMBLE EXEC HLASMC
//SYSLIB DD DISP=SHR,DSN=ASMA.SASMMAC1
// DD DISP=SHR,DSN=SYS1.MACLIB
// DD DISP=SHR,DSN=distribution.maclib
//C.SYSIN DD *
#svcopt source
/*
//LINK EXEC PGM=IEWL,PARM='NCAL,NOLIST,NOMAP,LIST=STMT'
//SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(20,20))
//SYSPRINT DD SYSOUT=*
//OBJLIB DD DISP=SHR,DSN=distribution.loadlib
//SYSLMOD DD output loadlib
//SYSLIN DD DISP=(OLD,DELETE),DSN=&&OBJ
// DD *
link edit statements
/

Outcomes