View previous topic :: View next topic
|
Author |
Message |
Ganesh Kalam Warnings : 1 New User
Joined: 11 Aug 2005 Posts: 45 Location: India
|
|
|
|
My requirement is like this,
I have to define a PSB with 30 PCBs, each PCB containing 13 segments. When i am doing so i am getting SOC1 abend. I tried many times, but getting same abend.
Is there any limitation on the number of segments defined in a PSB. |
|
Back to top |
|
|
priyesh.agrawal
Senior Member
Joined: 28 Mar 2005 Posts: 1448 Location: Chicago, IL
|
|
|
|
Quote: |
I have to define a PSB with 30 PCBs, each PCB containing 13 segments. When i am doing so i am getting SOC1 |
1 PSB
= 30 PCB
= 30 * (13 Segments)
= 390 Segments
There cant be more than 255 segments in a database. You should see your shop DBA first, while interacting such. |
|
Back to top |
|
|
guptae
Moderator
Joined: 14 Oct 2005 Posts: 1208 Location: Bangalore,India
|
|
|
|
Yeap Priyesh is right .There cant be more than 255 segments in a database.
But PSB Program specification Block is basically logical structure of the d/b which program will use which can belongs to different database and in that case it can be more than 255. |
|
Back to top |
|
|
priyesh.agrawal
Senior Member
Joined: 28 Mar 2005 Posts: 1448 Location: Chicago, IL
|
|
|
|
Ganesh... I am sorry for misunderstanding... I have that bad habit of answering without reading the question properly.
Anyway, I'll try to find answer and let you know.
Ekta... Thanks for noticing and correcting. |
|
Back to top |
|
|
PascalQ
New User
Joined: 12 May 2006 Posts: 20
|
|
|
|
Ganesh Kalam, please post the full error message.
Also: is it OC1 or 0C1? (I think the latter?). And: can you compile ANY PSB, i.e. with less than 390 segments it works fine?
As mentioned before, there's no such limit set by IMS. We have lots of PSBs with more than 400 segments. |
|
Back to top |
|
|
Bitneuker
CICS Moderator
Joined: 07 Nov 2005 Posts: 1104 Location: The Netherlands at Hole 19
|
|
|
|
@Topic starter: Could you please provide us with more information? When are you getting the error: during PSBGEN or while your application is running? If during PSBGEN please post the JCL. If during execution of your application post the content of the PSB and the entry in your program so we can find out whether your pointers are set in the correct order (though you should get an IMS-error code if that's the case). |
|
Back to top |
|
|
Ganesh Kalam Warnings : 1 New User
Joined: 11 Aug 2005 Posts: 45 Location: India
|
|
|
|
Hi friends,
Thank you very much for paying attention on this. Yes PascalQ you are right ..i am getting S0C1.. I mentioned SOC1 ..sorry for the typo...
Bitneuker.. I am getting this problem during PSBGEN.....I am using a tool to create the PSB...it will submit a background JCL.. When i am selecting segments around 200 it is working fine.. But the problem occurs when it is beyond 250...It is giving S0C1..without submitting a job...
I doubt whether we can select more than 255 segments even though they are from different databases.. Correct me if i am wrong..
Thanks to priyesh and Ekta..for inputs on this... |
|
Back to top |
|
|
Bitneuker
CICS Moderator
Joined: 07 Nov 2005 Posts: 1104 Location: The Netherlands at Hole 19
|
|
|
|
Ganesh,
A PSB may obtain one to many PCB's where each PCB represents one database. Each database is limited to 255 segments and this is watched during DBDGEN so I don't think it's the number of segments. If you need segments from different databases with the view of one logical database you should define (bi-)directional pointers.
Now to your problem:
You say the PSBGEN isn't submitted because the (submit)tool failes. Looks like there's your problem. I have no clue what your (submit)tool does and how it looks like. System errors like S0C1 usually point at an error in de DD/DCB. Could be possible your tool finds out you oversized and tries to send a warning. If the medium it uses to post the message lacks or is defined wrongly you might find yourself confronted with a S0C1.
So far I myself have the impression I'm guessing around so please post some more specific information like screenprints, dump and detailed information about the S0C1. |
|
Back to top |
|
|
|