|
View previous topic :: View next topic
|
| Author |
Message |
niks_jude
Warnings : 1
Active User
Joined: 01 Dec 2006
Posts: 144
Location: Mumbai
|
|
|
|
Hi,
I am inserting an immediate child P258ONE of P258SER root segment but getting V1 status. I have checked length of insert layout and DBD definition length of the segment match.
1. The DLI insert call
CALL 'CBLTDLI' USING ISRT
DB0258-PCB
P258ONE-IO-AREA
P258SER-SSA-Q
P258ONE-SSA-UNQUAL.
I have checked and correct PSB is picked.
2. Here is the PSB of the program.
PCB TYPE=DB,DBDNAME=DB0258,KEYLEN=99,
PCBNAME=DB0258R1,SB=COND
SENSEG NAME=P258SER,PARENT=0,PROCOPT=AP
SENSEG NAME=P258ONE,PARENT=P258SER,PROCOPT=AP
PSBGEN PSBNAME=P258ONEI,LANG=COBOL,CMPAT=YES
END
3. The segment layout from dump -
01 P258ONE-IO-AREA AN-GR
02 SEIMS-ONE-SEG AN-GR
03 ONE-SEG-LNGTH S9999 COMP +00000
03 ORIG-MER-ID X(15) DISP '0000001 '
03 CUR-MER-ID X(15) DISP ' '
03 CUR-MID-EFFTV-DATE
AN-GR
04 JULIAN-DATE S9(5) CMP3 +00000
03 FILLER X(465) DISP '
4. DBD definition pf P258ONE showing length of 500 bytes.
SEGM NAME=P258ONE,BYTES=(500,4),PTR=(NT),
PARENT=P258SER,RULES=(LLL,LAST),
COMPRTN=(DPIEXIT,DATA,INIT)
Please let me know in case of any other questions.[/code]
|
|
| Back to top |
|
 |
niks_jude
Warnings : 1
Active User
Joined: 01 Dec 2006
Posts: 144
Location: Mumbai
|
|
|
|
I did not know this but it was a varaiable segment so ONE-SEG-LNGTH had to be populated with proper length. It stopped giving V1 status code after this.
Then I tried inserting but it failed with status code AI. Is it because I am inserting in DLI mode, can we not insert in DLI mode.
I cannot try BMP because then I will have to define the PSB (having a new segment) through some formal procedures, which is not possible for my adhoc program. |
|
| Back to top |
|
|
don.leahy
Active Member
Joined: 06 Jul 2010
Posts: 765
Location: Whitby, ON, Canada
|
|
|
|
| Are your data base datasets specified in your JCL? |
|
| Back to top |
|
|
niks_jude
Warnings : 1
Active User
Joined: 01 Dec 2006
Posts: 144
Location: Mumbai
|
|
|
|
No. They are not.Here is my complete JCL.
| Code: |
//STEP010 EXEC PGM=DFSRRC00,REGION=0M,
// PARM=(DLI,P258ONEI,SE258UPD,,,,,,,,,,,N)
//STEPLIB DD DSN=CHGMAN.GMS1.#021104.LOD,DISP=SHR
// DD DSN=IMSVS.TEST.PRODUCTS,DISP=SHR
// DD DISP=SHR,DSN=IMSVS.IMSN.RESLIB
// DD DSN=ADC1.IPCW.PROD.LINKLIB,DISP=SHR
// DD DISP=SHR,DSN=IMSVS.IMSN.USERLIB
//IMS DD DISP=SHR,DSN=WXX830.NB0483A.PSBLIB
// DD DISP=SHR,DSN=IMSVS.IMSN.DBDLIB
//DFSRESLB DD DISP=SHR,DSN=IMSVS.IMSN.RESLIB
//IMSLOGR DD DUMMY,DSN=IM.LOG.SE250.SEM250,
// DISP=(OLD,KEEP,KEEP),
// DCB=IM.LOG.MODLDSCB,
// UNIT=SYSDA
//IEFRDER DD DSN=SSR.IM.LOG.SE250.SEM250,
// DISP=(NEW,DELETE,KEEP),
// DCB=IM.LOG.MODLDSCB,
// UNIT=SYSDA
//DFSVSAMP DD DISP=SHR,DSN=CHGMAN.GMSE.DATALIB(VSAMPDLI)
//CHKPFREQ DD DSN=CHGMAN.GMSE.DATALIB(SE250CHK),DISP=SHR
//SELSTFLE DD *
3122363310
4101822617
1429687726
/*
//SYSOUT DD SYSOUT=*
//SYSOUA DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSABOUT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//IMSERR DD SYSOUT=*
//CEEDUMP DD SYSOUT=*
//ABNLTERM DD SYSOUT=*
//DFSSTAT DD SYSOUT=* |
|
|
| Back to top |
|
|
don.leahy
Active Member
Joined: 06 Jul 2010
Posts: 765
Location: Whitby, ON, Canada
|
|
|
|
| That explains your AI status. |
|
| Back to top |
|
|
niks_jude
Warnings : 1
Active User
Joined: 01 Dec 2006
Posts: 144
Location: Mumbai
|
|
|
|
You mean had they been defined in my JCL I would have got the right to update them. But in our system I have never seen IMS datasets being defined in the JCL.
Can you please elaborate? |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
I don't "do" ims, but maybe this will apply anyway.
On many database systems, jobs run in "single user" mode allocate the database datasets within the job. The database activity takes place within the adddress space of the job. Without these allocations, the single user job will not even read the data, let alone update it.
Jobs run in "multiple user" mode use the the datasets allocated by the database processing address space - they are NOT defined in the job.
I'm not sure when/how the V1 status switched to AI . . . 
Maybe, i've not muddied the water. . . |
|
| Back to top |
|
|
don.leahy
Active Member
Joined: 06 Jul 2010
Posts: 765
Location: Whitby, ON, Canada
|
|
|
|
| niks_jude wrote: |
You mean had they been defined in my JCL I would have got the right to update them. But in our system I have never seen IMS datasets being defined in the JCL.
Can you please elaborate? |
Do you have any other DLI batch jobs in your shop? |
|
| Back to top |
|
|
niks_jude
Warnings : 1
Active User
Joined: 01 Dec 2006
Posts: 144
Location: Mumbai
|
|
|
|
Yes but none for updates to whatever extent I have seen.
Dick,
It changed from V1 to AI once I populated the length field of the variable segment. |
|
| Back to top |
|
|
don.leahy
Active Member
Joined: 06 Jul 2010
Posts: 765
Location: Whitby, ON, Canada
|
|
|
|
| Do any of your other calls to this data base work properly? |
|
| Back to top |
|
|
niks_jude
Warnings : 1
Active User
Joined: 01 Dec 2006
Posts: 144
Location: Mumbai
|
|
|
|
| Yes normal get calls work fine with DLI, its with updates that we get the abends in a DLI call? Is it our system enforced error or is it like IMS cannot insert in DLI mode? |
|
| Back to top |
|
|
don.leahy
Active Member
Joined: 06 Jul 2010
Posts: 765
Location: Whitby, ON, Canada
|
|
|
|
| Yes, IMS can insert in DLI mode. |
|
| Back to top |
|
|
niks_jude
Warnings : 1
Active User
Joined: 01 Dec 2006
Posts: 144
Location: Mumbai
|
|
|
|
| OK, Thanks. This looks to be our shop enforced restriction. |
|
| Back to top |
|
|
hchinnam
New User
Joined: 18 Oct 2006
Posts: 73
|
|
|
|
| Can't be. You MUST define your IMS datasets in the JOB if you want to use them in DLI mode. |
|
| Back to top |
|
|
don.leahy
Active Member
Joined: 06 Jul 2010
Posts: 765
Location: Whitby, ON, Canada
|
|
|
|
| Are you seeing message DFS0730I? |
|
| Back to top |
|
|
niks_jude
Warnings : 1
Active User
Joined: 01 Dec 2006
Posts: 144
Location: Mumbai
|
|
|
|
Hchinnam,
I have posted my JCL above....believe me or not it is complete and it does not show any IMS DB datasets.
Don,
You are bang on target. I think we have JCLs setup in the system so that no DLI has the IMS dataset defined. I guess it is added dynamically becuase for same JCL posted above I am getting this error and AI status code in insert. Because read always work fine with DLI.
| Code: |
JOB13641 +BMC2700 API BYPASSED -- NO PLUSIN DD PRESENT BMC
JOB13641 ICH408I USER(NB0483A ) GROUP(G31 ) NAME(*********, *****
SEUSAO.TEST.DB0258A.PDF CL(DATASET ) VOL(BOZAE9)
INSUFFICIENT ACCESS AUTHORITY
FROM SEUSAO.* (G)
ACCESS INTENT(UPDATE ) ACCESS ALLOWED(READ )
JOB13641 IEC150I 913-38,IFG0194E,NB0483A1,STEP010,DB0258A,D5AC,BOZAE9,
JOB13641 DFS0695I OSAM OPEN INTERCEPT,ABEND=913-38,DDN=DB0258A
JOB13641 +DFS0730I UNABLE TO OPEN DATA SET WITH DDNAME DB0258A FOR R
JOB13641 +AB400A ===== ABEND-AID ===== 872
REPORT WRITTEN TO: SYSS.ABENDAID.RPTDIR
REPORT NUMBER: 0200682
JOB-NB0483A1 STEP-STEP010
LE COND CODE=CEE3501S / EXPECTED COMP CODE=S806
TYPE "TSO AAUTIL" FROM THE COMMAND LINE TO VIEW REPORT
JOB13641 +CWFM 0057 E PUBX, CANNOT LOCATE PAB, RC = 00 |
|
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Suggest you investigate the s913 security abend. . .
| Code: |
INSUFFICIENT ACCESS AUTHORITY
FROM SEUSAO.* (G)
ACCESS INTENT(UPDATE ) ACCESS ALLOWED(READ ) |
|
|
| Back to top |
|
|
niks_jude
Warnings : 1
Active User
Joined: 01 Dec 2006
Posts: 144
Location: Mumbai
|
|
|
|
| Yes I guess in DLI mode they have given read only access to IMS datasets. |
|
| Back to top |
|
|
|
|
