Getting V1 IMS status code on ISRT call.

vardhan0007 · Posted: Thu Apr 03, 2008 8:17 pm

Hi All,

I am facing the issue with one of my insert call. I am gettinf V1 status code.Please le t me know what amy be the reason.
the below is the reason which i got from IBM sources.
V1
Explanation:
The program tried to insert or replace a variable-length segment that is too long. The length of the segment must be equal to or less than the maximum length specified in the DBD. IMS also returns status code V1 when the specified minimum length cannot hold the complete sequence field of the segment type. In this situation, status code V1 results from one of three instances: processing without an edit/compression routine; processing with an edit/compression routine, but not specifying the key compression option; or coding a length field (LL) that is less than the specified minimum length. The length must be long enough to include the entire reference field; if the segment is a logical child, it must include the entire concatenated key of the logical parent and all sequence fields for the paired segment. The program tried to delete a variable-length segment. The copy of this segment in the user's I/O area contains an invalid length field.

IMS also returns this status code when an invalid record length is specified in a GSAM call.

Can anyone explain in detail each condition.

Thanks in advance.
Harsha.

Bitneuker · Posted: Thu Apr 03, 2008 8:57 pm

I Think the explanation speaks for itself...... What specific part would you like to have explained better??? And you also should tell us if any logical relationship is involved.

Sandy Zimmer · Posted: Mon Apr 07, 2008 7:28 pm

Also, if it is a variable length segment.

sasikumar1984 · Posted: Thu Apr 10, 2008 6:54 am

Hi Vardhan,

Can you please increase the occurs if it uses for the GSAM file to which ur inserting and check it. We usually get V1 when the data of the current insertion GSAM file is merged with some other data. I had similar kind of issue sometime back. Which i have solved by increasing the occurs class and solved the problem.