Does the maximum record length of a queue record depend on the page size of DDLDCRUN? Will a queue record span multiple pages with DCRUN? Or must a queue record fit on a page?
Unless something changed, Queue and Scratch records are instantiated as
one SROOT-*** (139?) and 0-n SEXT-yyy (140?) records, so no, it should not
be constrained by page size.
But it has been a while.
Service Delivery Manager - Mainframe
IMG/Service Transition and Operations/Service Operations
Kaiser Permanente Information Technology
NOTICE TO RECIPIENT: If you are not the intended recipient of this
e-mail, you are prohibited from sharing, copying, or otherwise using or
disclosing its contents. If you have received this e-mail in error,
please notify the sender immediately by reply e-mail and permanently
delete this e-mail and any attachments without reading, forwarding or
saving them. Thank you.
Don,I'm not aware of the store process changing fir scratch or queue records. They are both stored as a root and 0 or more extension records.Chuck
Bob, did Don and Chuck's input help you with your problem? Let us know!
Looks like you have this answer but to reiterate:
When a queue record is written an SROOT-DCS-139 record is created. If the queue record is less than 500 bytes it will fit entirely in that record occurrence. If the queue record is greater than 500 bytes the first 500 go into the SROOT-DCS-139 record and the remaining length is spread across one or more SEXT-DCS-140 records. Each SEXT-DCS-140 record can hold up to 500 bytes. The SROOT-DCS-139 owns the SEXT-DCS-140 record through a standard chained set so the number of members is unlimited so the length of the record from a DB standpoint is unlimited.
And it if is a Queue, not a Scratch, the 139s are owned by a ***-DCQ-138,
calc on queue name, through an OM set. Yes?
Hi Don! Yes the header record for a Queue is the QUEUE-DCQ-138 record. The actual user content is stored in the 139 and possibly one or more 140 records
Retrieving data ...