Quantcast
Channel: IBM Mainframe Computers Forums
Viewing all 8500 articles
Browse latest View live

CICS :: RE: Mantis Program Compiled?


DB2 :: RE: LOW VALUES as a KEY

$
0
0
Author: juares castro
Posted: Mon Apr 09, 2018 6:57 pm (GMT 5.5)

Thanks to everyone!

And, Phrzby Phil, my understanding about the forum is share what we know and about our experience to help anybody. Indeed I could try first, but I have chosen searching here. It is a good manner to me to learn something.
_________________
Thanks!
juares castro

DB2 :: RE: LOW VALUES as a KEY

$
0
0
Author: Phrzby Phil
Posted: Mon Apr 09, 2018 7:19 pm (GMT 5.5)

Juares -

I certainly agree with your comments about sharing. My intention is merely to encourage anyone new to technology (and this includes experts on this excellent forum who may from time to time be using certain tools for the first time) to learn as much as possible by experimenting. The lessons will stick much more rapidly and solidly this way.

When I was getting more involved with DB2, I had a sandbox set up for me where I could play around and try all kinds of stuff (e.g., experimenting with the so-called null indicator - "so-called" because if I remember, it indicates other stuff as well. Anyone wanting to clarify this please do.)

This also provided me with a collection of experiments and tests i could then build on and share with my team.

I'm retired now, but I wish you Good Luck and Happy Hunting.

Live Long and Prosper.
_________________
World Peace Through Frisbee.

DB2 :: RE: LOW VALUES as a KEY

$
0
0
Author: juares castro
Subject: Reply to: LOW VALUES as a KEY
Posted: Mon Apr 09, 2018 10:09 pm (GMT 5.5)

Thanks Phrzby Phil !
Long life for You too.
_________________
Thanks!
juares castro

DB2 :: RE: LOW VALUES as a KEY

$
0
0
Author: Rohit Umarjikar
Posted: Mon Apr 09, 2018 10:36 pm (GMT 5.5)

I think , my point was not clearly presented.
Why would need to add low values to a key field? just eliminate if that's junk before you load the DB2.
_________________
Regards,
Rohit Umarjikar
A leader is one who knows the way, goes the way, and shows the way.

COBOL Programming :: RE: COBOL MVS options

$
0
0
Author: BiswajitDG
Subject: Reply to: COBOL MVS options
Posted: Mon Apr 09, 2018 11:22 pm (GMT 5.5)

Robert - Apologies and will address you by your first name going forward.

DB2 :: RE: LOW VALUES as a KEY

$
0
0
Author: juares castro
Posted: Mon Apr 09, 2018 11:36 pm (GMT 5.5)

Hi Rohit Umarjikar!
As I said before, we will convert our process to JAVA/LINUX and the current file is a VSAM, that is not supported in LINUX. And in this file first record has LOW-VALUES (X'0000...00') as key. That was my question.
_________________
Thanks!
juares castro

DB2 :: RE: LOW VALUES as a KEY

$
0
0
Author: enrico-sorichetti
Subject: Reply to: LOW VALUES as a KEY
Posted: Tue Apr 10, 2018 11:24 am (GMT 5.5)

as already told ...
the data(base) management systems DO NOT CARE about the values of the keys
so any discussion why the TS want to use a "low value" is just a completely waste of time.

the topic has been pruned of the irrelevant posts
_________________
cheers
enrico
When I tell somebody to RTFM or STFW I usually have the page open in another tab/window of my browser,
so that I am sure that the information requested can be reached with a very small effort icon_cool.gif


IMS DB/DC :: Getting GG return code

$
0
0
Author: abdulrafi
Subject: Getting GG return code
Posted: Tue Apr 10, 2018 12:31 pm (GMT 5.5)

Hi,

I am executing a IMS program which just retrieves the data from a segment but I am getting GG. I verified in the manuals and read the below information from this link. I did what has been said as programmer response, but could not resolve this. Need your help in resolving it.
https://www.ibm.com/support/knowledgecenter/en/SSEPH2_13.1.0/com.ibm.ims13.doc.msgs/msgs/gg.htm

JCL:


Code:

//JS010   EXEC TST1BTCH,MBR=ISMB305,PSB=PIPSCN1                 
XXTST1BTCH PROC MBR=TEMPNAME,SOUT='*',PSB=,BUF=,NODE1=IMSF1,   
XX             NODE2=IMSF1,SPIE=0,TEST=0,EXCPVR=0,RST=0,       
XX             PRLD=,SRCH=0,CKPTID=,MON=N,LOGA=,FMTO=,         
XX             IMSID=TST1,SWAP=,RGN=0K,DBRC=,IRLM=,IRLMNM=,     
XX             BKO=,IOBF=00,USERLIB=SYS1VR.ENDEVOR.DEV.LOADLIB 
XXG        EXEC PGM=DFSRRC00,REGION=&RGN,                       
XX             PARM=(DLI,&MBR,&PSB,&BUF,                       
XX             &SPIE&TEST&EXCPVR&RST,&PRLD,                     
XX             &SRCH,&CKPTID,&MON,&LOGA,&FMTO,                 
XX             &IMSID,&SWAP,&DBRC,&IRLM,&IRLMNM,&BKO)           
IEFC653I SUBSTITUTION JCL - PGM=DFSRRC00,REGION=0K,PARM=(DLI,ISMB305,PIPSCN1,,0000,,0,,N,,,TST1,,,,,)
XXSTEPLIB  DD  DSN=&NODE1..RESLIB,DISP=SHR                     
IEFC653I SUBSTITUTION JCL - DSN=IMSF1.RESLIB,DISP=SHR           
XX         DD  DSN=SYS1VR.IBMTOOL.DBG.TEMPLOAD,DISP=SHR         
XX         DD  DSN=SYS1VR.ENDEVOR.DEV.LOADLIB,DISP=SHR         
XX         DD  DSN=SYS1VR.ENDEVOR.STAGING.LOADLIB,DISP=SHR     
XX         DD  DSN=SYS1VR.ENDEVOR.TMMK.PROD.LOADLIB,DISP=SHR   
XX         DD  DSN=SYS1VR.ENDEVOR.TMMNA.PROD.LOADLIB,DISP=SHR   
XX         DD  DSN=SYS1VR.ENDEVOR.TMMI.PROD.LOADLIB,DISP=SHR       
XX         DD  DSN=SYS1VR.ENDEVOR.TMMW.PROD.LOADLIB,DISP=SHR       
XX         DD  DSN=SYS1VR.ENDEVOR.COMMON.PROD.LOADLIB,DISP=SHR     
XX         DD  DSN=&USERLIB,DISP=SHR                               
IEFC653I SUBSTITUTION JCL - DSN=SYS1VR.ENDEVOR.DEV.LOADLIB,DISP=SHR
XX         DD  DSN=TISM.PGP.LOADLIB,DISP=SHR                       
XX         DD  DSN=SYS1.UTLIB,DISP=SHR                             
XX         DD  DSN=PCS.PGMLIB,DISP=SHR                             
XX*        DD  DSN=SYS1V.XCH1FDN.LOAD,DISP=SHR                     
XXDFSRESLB DD  DSN=&NODE1..RESLIB,DISP=SHR                         
IEFC653I SUBSTITUTION JCL - DSN=IMSF1.RESLIB,DISP=SHR             
XXIMS      DD  DSN=&NODE1..PSBLIB,DISP=SHR                         
IEFC653I SUBSTITUTION JCL - DSN=IMSF1.PSBLIB,DISP=SHR             
XX         DD  DSN=&NODE2..DBDLIB,DISP=SHR                         
IEFC653I SUBSTITUTION JCL - DSN=IMSF1.DBDLIB,DISP=SHR             
XXPROCLIB  DD  DSN=&NODE1..PROCLIB,DISP=SHR                       
XX*XGIMSREQ DD  DSN=SYS1V.XCH1FDN.REQUEST.FILE,DISP=SHR           
IEFC653I SUBSTITUTION JCL - DSN=IMSF1.PROCLIB,DISP=SHR             
XXIEFRDER  DD  DUMMY                                               
XXPLIDUMP  DD  SYSOUT=*                                             
XXSYSPRINT DD  SYSOUT=&SOUT                                         
IEFC653I SUBSTITUTION JCL - SYSOUT=*                               
XXSYSOUT   DD  SYSOUT=&SOUT                                         
IEFC653I SUBSTITUTION JCL - SYSOUT=*                               
XXSYSOUZ   DD  SYSOUT=&SOUT                                         
IEFC653I SUBSTITUTION JCL - SYSOUT=*                               
XXSYSUDUMP DD  SYSOUT=*                                             
XXIMSMON   DD  DUMMY                                               
XXDFSVSAMP DD  DISP=SHR,DSN=&NODE1..PROCLIB(DFSVSM&IOBF)           
XX*CLEANUP EXEC PGM=XGCLNREQ,COND=EVEN                             
XX*STEPLIB  DD  DSN=SYS1V.XCH1FDN.LOAD,DISP=SHR                     
XX*XGIMSREQ DD  DSN=SYS1V.XCH1FDN.REQUEST.FILE,DISP=SHR             
//*                                                                 
IEFC653I SUBSTITUTION JCL - DISP=SHR,DSN=IMSF1.PROCLIB(DFSVSM00)   
//PIPDCN0  DD  DISP=SHR,DSN=TPIP.T25.CNI.PIPDCN0.PIPECONT 
//PIPDCN1  DD  DISP=SHR,DSN=TPIP.T25.CNI.PIPDCN1.PIPEINDX 
//PIPDCN2  DD  DISP=SHR,DSN=TPIP.T25.CNI.PIPDCN2.PIPESIXP 
//OUT01    DD  DSN=TPIP.T25.DB.DUMP,   
//             DISP=OLD               


PSB:
Code:

PCB    TYPE=DB,DBDNAME=PIPDCN0,PROCOPT=GOTP,KEYLEN=050   
SENSEG NAME=PIPECN00,PARENT=0                             
SENSEG NAME=PIPECN01,PARENT=PIPECN00                     
SENSEG NAME=PIPECN02,PARENT=PIPECN01                     
PSBGEN PSBNAME=PIPSCN1,LANG=PL/I,CMPAT=YES               
END                                                       
[/url]
_________________
Thanks,
Abdul Rafi

IMS DB/DC :: RE: Getting GG return code

$
0
0
Author: abdulrafi
Posted: Tue Apr 10, 2018 12:40 pm (GMT 5.5)

This is the error I received,

Code:
DFS035I BATCH INITIALIZATION COMPLETE  TST1                 
          ISMB305 START                                     
          XXXXXXXXXX ISMB305 ABEND                         
          STCD = GG   SEGMENT = PIPECN00                       

_________________
Thanks,
Abdul Rafi

JCL & VSAM :: RE: Unavailable RECON datasets while executing IMS BACKUP

$
0
0
Author: abdulrafi
Posted: Tue Apr 10, 2018 10:08 pm (GMT 5.5)

Hi,

I tried to give the RECON data sets, it showed me insufficient access authority.
I got an error telling, INTENT (UPDATE) ACCESS (READ), even though I am only taking backup.

So i thought it might be because of the DB being running. So I stopped the DB and then executed it in DLI mode. But even then I got the same access authority error telling that my intent is to UPDATE the DB rather than reading.

Could you please assist. I do also have a plan to discuss with DBA.
_________________
Thanks,
Abdul Rafi

DB2 :: RE: LOW VALUES as a KEY

$
0
0
Author: juares castro
Posted: Tue Apr 10, 2018 10:22 pm (GMT 5.5)

Enrico, i was just responding Phrzby Phi.
_________________
Thanks!
juares castro

IMS DB/DC :: RE: Getting GG return code

$
0
0
Author: Gary Jacek
Posted: Tue Apr 10, 2018 10:41 pm (GMT 5.5)

If your database datasets shown below are not used by any other job or task then the chance of a database pointer repairing itself to allow your GG status code to go away, is zero.

//PIPDCN0 DD DISP=SHR,DSN=TPIP.T25.CNI.PIPDCN0.PIPECONT
//PIPDCN1 DD DISP=SHR,DSN=TPIP.T25.CNI.PIPDCN1.PIPEINDX
//PIPDCN2 DD DISP=SHR,DSN=TPIP.T25.CNI.PIPDCN2.PIPESIXP

So you must ask, who created these datasets? Were they created while updates were in flight against them? That would certainly explain broken pointers.

DB2 :: RE: LOW VALUES as a KEY

$
0
0
Author: enrico-sorichetti
Subject: Reply to: LOW VALUES as a KEY
Posted: Tue Apr 10, 2018 11:36 pm (GMT 5.5)

I was not commenting Your posts,
but the posts of the people questioning the why of a key containing low values
_________________
cheers
enrico
When I tell somebody to RTFM or STFW I usually have the page open in another tab/window of my browser,
so that I am sure that the information requested can be reached with a very small effort icon_cool.gif

JCL & VSAM :: RE: Unavailable RECON datasets while executing IMS BACKUP

$
0
0
Author: enrico-sorichetti
Subject: Reply to: Unavailable RECON datasets while executing IMS BACKUP
Posted: Tue Apr 10, 2018 11:38 pm (GMT 5.5)

NO we will not assist, the problem must be solved by your DBA,
planning to ask is not enough.

topic locked
_________________
cheers
enrico
When I tell somebody to RTFM or STFW I usually have the page open in another tab/window of my browser,
so that I am sure that the information requested can be reached with a very small effort icon_cool.gif


PL/I & Assembler :: Default attributes for undeclared SYSPRINT in PL/1

$
0
0
Author: Alan Playford
Subject: Default attributes for undeclared SYSPRINT in PL/1
Posted: Wed Apr 11, 2018 5:18 pm (GMT 5.5)

Guys,
We have a PL/1 program (inherited, one of many) which issues a DISPLAY to put information to the SYSPRINT file.
In the JCL it is pre-allocated first as a PS-FB-121-6050 dataset.
This is then defined in the PL/1 run step and allocated to the SYSPRINT DD statement.
It is NOT DECLAREd in the program itself (this is apparently not a neccessity!)

Running the program appears to change this PS-FB-121-6050 dataset to a PS-VB-1028-6144 dataset.

The DISPLAYed data appears there happily.
However, for logistical reasons I can't go into, this is too large and we really want to use the PS-FB-121 (or thereabouts) pre-allocated values instead.

Does anybody know how to circumvent this, or where the defaults are stored when SYSPRINT is dynamically allocated or used by PL/1?

Program appears below:
Code:
 ABCPROG: PROC OPTIONS(MAIN);                                         
  /*** WITHOUT THE FILE DCL THE LRECL BECOMES 1028 TOO BIG        ***/ 
   DISPLAY('BEGIN');                                                   
   DCL TAB(100:199) BIT(1) ALIGNED;                                   
   DCL II FIXED     BIN(15) INIT(10);                                 
   DISPLAY('Storage:  '  || CSTG(TAB)                                 
                         || '  LBound:  '                             
                         || LBOUND(TAB, 1)                             
                         || '  HBound:  '                             
                         || HBOUND(TAB, 1)                             
                         || ' ');                                     
    DISPLAY(TAB(II*6+100) || TAB(II*6+101));                           
    TAB(II*6+100) = '1'B;                                             
    DISPLAY(TAB(II*6+100) || TAB(II*6+101));                           
    TAB(II*6+100) = '0'B;                                             
    DISPLAY(TAB(II*6+100) || TAB(II*6+101));                           
    DISPLAY('END');                                                   
  END;  /*ABCPROG*/


and output below:

Code:
BEGIN

Storage:             100  LBound:             100  HBound:             199

11

11

01

END

_________________
Alan Playford

PL/I & Assembler :: RE: Default attributes for undeclared SYSPRINT in PL/1

$
0
0
Author: steve-myers
Posted: Wed Apr 11, 2018 7:34 pm (GMT 5.5)

I am no PL/I expert; I can't answer your query directly. I would like to make a couple of observations.
  • Personally, I do not think the PL/I library should be changing the DCB attributes of the data set specified by the DD statement with DD name SYSPRINT. I think this is an issue you should pursue with IBM. Unfortunately there is no truly "right" answer for this issue so you may find IBM's response less than satisfactory to you. Perhaps true PL/I experts might have more input than I can provide.
  • I do not think inserting tab characters into a data set will result in the behavior you expect. No IBM printer that I know about provides a tab type function, and the PL/I library does not seem to respond to tab characters by inserting the appropriate blanks into the final output line.
  • Based on the Language Reference manual, you can achieve a tab like capability by using COLUMNnnn) in PUT EDIT statements. The Language Reference manual also mentions X(nnn) to "place blank characters in line to establish position," though this does not seem to be a tab type function.
  • It has been my experience that most of the time data sets specified as having variable length records require less space than data sets specified with fixed length records mainly because it is easy to remove trailing blanks in the output line. Roughly 40 years ago I decided to generally prepare data sets with variable length records; other than complaints from people that want to write programs to reprocess print type data sets who are not accustomed to handling VB data sets there have been few problems.

JCL & VSAM :: VSAM - Accessing beyond record size

$
0
0
Author: Benchwarmer
Subject: VSAM - Accessing beyond record size
Posted: Wed Apr 11, 2018 9:20 pm (GMT 5.5)

A VSAM file is received from a external source. The layout of the VSAM file is as below

Code:
01  VSAM-FILE                                           
    05  VSAM-RECORD-KEY              PIC X(10).         
    05  VSAM-OCCUR-CT                PIC 9(2) VALUE 1. 
    05  VSAM-DATA-SEG OCCURS  1 TO 10 TIMES             
           DEPENDING ON VSAM-OCCUR-CT.                 
        10  VSAM-NAME                PIC X(45).         


For some reason, the program consuming the VSAM file is looking at all occurrences to verify data exist and match against the count provided in input.

I expected the program will fail with return code '14 - Attempted to READ a relative record outside file boundary'

I tried debugging the code by reading the file and see the values for occurrences beyond the count is Null.

I searched in google and but did not find anything relative. Any pointers on how this works?

JCL & VSAM :: RE: VSAM - Accessing beyond record size

$
0
0
Author: Robert Sample
Subject: Reply to: VSAM - Accessing beyond record size
Posted: Wed Apr 11, 2018 9:31 pm (GMT 5.5)

Are you talking about a COBOL program (I assume this since the provided CODE is COBOL)? If so, is the program doing a READ or READ INTO? Based upon your comment, I assume your program is doing READ. In such a case, when COBOL does the READ, the VSAM-RECORD-KEY and VSAM-OCCUR-CT are read from the data set, then the VSAM-DATA-SEG occurrences are read (limited to VSAM-OCCUR-CT occurrences). I'm not sure why you expect the file status 14, since it only applies to relative record data sets and a KSDS is not RRDS. You would be more likely to get file status 92 (or possibly 34 depending upon how the KSDS was opened) but as long as VSAM-OCCUR-CT is between 01 and 10 you should get a file status 00.
_________________
TANSTAAFL

The first rule of code reuse is that the code needs to be worth re-using.

"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth

CICS :: VSAM file NOT Found error while processing in a CICS Program

$
0
0
Author: SumaReva
Subject: VSAM file NOT Found error while processing in a CICS Program
Posted: Wed Apr 11, 2018 9:54 pm (GMT 5.5)

Hello All,
I am trying to trigger a CICS program and I am using VSAM file with Read command in it. Even though I have Defined the VSAM file in FCT and its attributes, the CICS program abends with FILE NOT found issue. Please help if I am missing something.

Code:
 Command  . . . : READ           
 File ID  . . . : VSHIPXXX       
 EIBRESP  . . . : 13 (NOTFND)     
 EIBRESP2 . . . : X'00000050'     
 EIBRCODE . . . : X'810000000000'


Read command in Program CMMXXX:

Code:
SPEC-SAP-SHIPVRY-DS            PIC X(08)  VALUE 'VSHIPXXX'.
SPEC-SAP-SHIPVRY-RL            PIC 9(4) COMP VALUE      700.
SPEC-SAP-SHIPVRY-KEY.       
05  SPEC-SAP-SHIPVRY-EVENXXX   PIC X(18).                                 

Code:
EXEC CICS READ                       
     DATASET ( SPEC-SAP-SHIPXXX-DS )
     INTO ( SHIPVXXX-RECORD)         
     RIDFLD ( SPEC-SAP-SHIPXXX-KEY )
     LENGTH (SPEC-SAP-SHIPXXX-RL)   
     RESP ( WS-LOG-STATUS )         
END-EXEC                             

Abend:

Code:
Program Offsete Function   Resource      Response
--------------------------------------------------
CMMXXX  9D0e     READ      VSHIPXXX      NOTFND

Viewing all 8500 articles
Browse latest View live