Sorry about delay in reply. Was at home and got caught up in other things. In the LISTCAT, you need to look at the values in AVGLRECL and MAXLRECL. In the VSAM DEFINE, you can have RECORDSIZE(avg max). No offense, but it sounds like you could use some basic VSAM training (not my forte, BTW).
You may be surprised to be told that, in VSAM, there really isn't such a thing as a fixed length record size. Oh, you can specify RECORDSIZE(n n) where "n" is supposedly the "fixed record size". And guess what? VSAM doesn't care if you write a record which is "too short" or "too long" according to those values. The only thing you cannot do is write a record larger than the CISIZE minus 4(?). And if you define the cluster with the SPANNED attribute, you can write a record which spans multiple CIs up to an entire CA in length (minus overhead of 4 bytes per CI). Again, your problem is _most likely_ that you have too many base records with a given alternate key. And I'd bet that key is one of ALL SPACES, ALL LOW-VALUES, or ALL HIGH-VALUES. But I could be wrong. Perhaps it is something like a zipcode. Or phone area code. I guess it depends on what your alternate index is based on. We had this exact problem where the alternate key was LOW-VALUES because the programmer used that for "unknown". The programmer then wanted to have VSAM modified so that it would not maintain an alternate key when the value was LOW-VALUES, but would for any other value. Like I had the source to VSAM and could modify it to meet his desires. Most weird to me. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * [email protected] * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of John Weber > Sent: Monday, November 19, 2012 7:37 PM > To: [email protected] > Subject: Re: VSAM Return Code 44 Received on Write to Fixed Length File > > What are we looking for in the LISTCAT output? RECORDSIZE is not > found. Is this because our VSAM file has a fixed length? Thanks. > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of John McKown > Sent: Monday, November 19, 2012 5:10 PM > To: [email protected] > Subject: Re: VSAM Return Code 44 Received on Write to Fixed Length File > > Then u get some default. Do a LISTC on the AIX to see what it is. You > might want to PRINT the records in the AIX itself just to see. Or on an > EXAMINE on it. > On Nov 19, 2012 6:52 PM, "John Weber" <[email protected]> wrote: > > > Interesting about a secondary status variable. We'll investigate > that. > > > > Regarding the AIX definitions. We do not include a RECORDSIZE > parameter. > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] > > On Behalf Of John McKown > > Sent: Monday, November 19, 2012 4:44 PM > > To: [email protected] > > Subject: Re: VSAM Return Code 44 Received on Write to Fixed Length > > File > > > > My habit with VSAM is to use the second COBOL FILE STATUS variable to > > get the actual VSAM return and reason codes. Often that is the only > > way to determine the actual reason. > > > > What comes to mind in your case is that the RECORDSIZE on your AIX is > > too small to record all the base keys associated with a single AIX > > key. This can cause a 44. Normally these keys are either ALL SPACES > or > > ALL LOW-VALUES or maybe ALL HIGH-VALUES. > > On Nov 19, 2012 6:21 PM, "John Weber" <[email protected]> wrote: > > > > > The only sysprint from the job is the status code display from the > > program. > > > > > > -----Original Message----- > > > From: IBM Mainframe Discussion List > > > [mailto:[email protected]] On Behalf Of Lizette Koehler > > > Sent: Monday, November 19, 2012 3:28 PM > > > To: [email protected] > > > Subject: Re: VSAM Return Code 44 Received on Write to Fixed Length > > > File > > > > > > Could you post the IDC messages for the 44? > > > > > > Lizette > > > > > > > > > -----Original Message----- > > > >From: John Weber <[email protected]> > > > >Sent: Nov 19, 2012 4:11 PM > > > >To: [email protected] > > > >Subject: VSAM Return Code 44 Received on Write to Fixed Length > File > > > > > > > >We are using a batch process to write account records to a VSAM > > > >file while also writing records to an audit file which is also a > VSAM file. > > > > > > > >Both files include an index and several alternate indexes. > > > >Each alternate index allows duplicates (NONUNIQUEKEY). > > > > > > > >The audit file receives a VSAM return code of 44 and discontinues > > > >writing after writing 3,258 of 10,000 records. > > > > > > > >Neither file is a variable file so the explanation of return code > > > >44 is not relevant to the problem or solution. (44 - REWRITE of > > > >different size record) > > > > > > > >The sizing in our allocations of our primary data and secondary > > > >index elements are appropriate for both files given the data in > this exercise. > > > > > > > >Please advise on problem solving this issue and/or what additional > > > information is needed. > > > > > > > >Thank you... > > > > > > > >John > > > > > > > >------------------------------------------------------------------ > - > > > >-- > > > >- For IBM-MAIN subscribe / signoff / archive access instructions, > > > >send email to [email protected] with the message: INFO > > > >IBM-MAIN > > > > > > ------------------------------------------------------------------- > - > > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to [email protected] with the message: INFO > > > IBM-MAIN > > > > > > > > > ------------------------------------------------------------------- > - > > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to [email protected] with the message: INFO > > > IBM-MAIN > > > > > > > --------------------------------------------------------------------- > - > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] with the message: INFO IBM-MAIN > > > > --------------------------------------------------------------------- > - > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
