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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Monday, November 19, 2012 4:44 PM To: IBM-MAIN@LISTSERV.UA.EDU 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" <j...@fiteq.com> wrote: > The only sysprint from the job is the status code display from the program. > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Lizette Koehler > Sent: Monday, November 19, 2012 3:28 PM > To: IBM-MAIN@LISTSERV.UA.EDU > 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 <j...@fiteq.com> > >Sent: Nov 19, 2012 4:11 PM > >To: IBM-MAIN@LISTSERV.UA.EDU > >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 lists...@listserv.ua.edu with the message: INFO > >IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
