A011 Vsam - Open Error - File
Contents |
+ productResults.length + resourceResults.length > 0 ? 'See all Search Results' : 'Full site search'}} > CA Support Online > KB Article CA Easytrieve Plus batch jobs abend with A011 VSAM - OPEN ERROR - FILE xxxxx - CODE vsam open error 160 136(88) since installing DBCS option. CA Easytrieve Plus batch jobs abend
Vsam Open Error 91
with A011 VSAM - OPEN ERROR - FILE xxxxx - CODE 136(88) since installing DBCS option. Document vsam open error a8 ID:TEC479303 Last Modified Date:4/2/2013 ShowHide Technical Document Details Products CA Easytrieve Report Generator CA Endevor Software Change Manager Components CA Easytrieve Plus Report Generator Description We have vsam open error 93 Easytrieve batch abends A011 VSAM - OPEN ERROR - FILE - CODE 136(88)and have resolved it by specifying a bigger REGION size. These jobs have not failed before and we only got the abend after migrating from CA Easytrieve 6.4 0311 to CA Easytrieve 6.4 0311 with the DBCS option installed. We would like to
Vsam Open Error 168
know if there are any software behavior changes when the DBCS option is enabled. Solution The cause of the OPEN error 136(88) is :"Not enough virtual storage space is available in your program's address space for work areas, control blocks, or buffers." This is because the size of the Easytrieve program itself is increased due to using the DBCS option, due to the number and size of the DBCS modules that are generated when you install this option.This is why you need to specify a bigger REGION size when using the DBCS option. Not what you were looking for? Search Again> Product Information Support by Product> Product Documentation> Communities Join a Community> Education Find training by product> Please help us improve! Will this information enable you to resolve your issue? Yes No Please tell us what we can do better. Char: Share × Contact us Privacy Policy Legal Notices Data Transfers Site Map Copyright © 2016 CA. All rights reserved.
Author Message kaviBeginnerJoined: 15 Sep 2006Posts: 64Topics: 22 Posted: Thu Jun 02, 2011 6:46 am Post subject: VSAM logical error Hi All, I have a KSDS file with Alternate Index. Am trying to read alternate index(PATH) with a key, during this read http://www.mvsforums.com/helpboards/viewtopic.php?p=57972&sid=1d4acda24a0a6c45c89265b93f8fbb75 am getting logical error 90 for this key, if i read another key i dont have any problem, when i manually checked this key in PATH, thru File manager, it got terminated, but the record is available in AIX and KSDS. http://stackoverflow.com/questions/7332104/vsam-status-code-04 I am using EZT for programming. The below is the error code. Any help on this would be appreciated. Code: A011 VSAM - LOGICAL ERROR - FILE XXXX - CODE 144(90) Is there any possiblity for base and AIX open error (path) not in sync. My KSDS define already used UPDATE Thanks, Kavi Back to top kolusuSite AdminJoined: 26 Nov 2002Posts: 11543Topics: 74Location: San Jose Posted: Thu Jun 02, 2011 8:49 am Post subject: kavi, Looks like you have a corrupted vsam file. The file status code 90 is returned when you encounter an invalid pointer (no associated base record) in an Alternate Index or a file status code 90 is returned when the file i-o result was that a bad open vsam open error file error occurrerd. This could be caused by a number of reasons, the most likely is that the file was not properly closed to start with. Run an idcams verify on the vsam file and re-run your ezt program. Kolusu Kolusu_________________Kolusu - DFSORT Development Team (IBM) DFSORT is on the Web at: www.ibm.com/storage/dfsort Back to top kaviBeginnerJoined: 15 Sep 2006Posts: 64Topics: 22 Posted: Thu Jun 02, 2011 9:04 am Post subject: Thanks Kolusu, This was happend in production toady. When we analyzed, found that, yesterday reorg was done for this VSAM file. So this might cause the problem. Running verify will solve the problem, or it could be some thing else? Can you please explain how the verify will work on VSAM file. Thanks, Kavi Back to top kolusuSite AdminJoined: 26 Nov 2002Posts: 11543Topics: 74Location: San Jose Posted: Thu Jun 02, 2011 9:14 am Post subject: kavi wrote: yesterday reorg was done for this VSAM file. So this might cause the problem. Never knew a Re-org can be done on a VSAM file. How did you re-org a vsam file? kavi wrote: Can you please explain how the verify will work on VSAM file. Read Chapter 3.4 which will explain Verify command in Detail www.redbooks.ibm.com/redbooks/pdfs/sg246105.pdf Kolusu Back to top papadiSupermodJoined: 20 Oct 2009Posts: 594Topics: 1 Posted: Thu Jun 02, 2011 3:11 pm Post subject: I suspect you mean an unload/reload of the data was done to accomplish the "re-org". This (run conrrectl
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up VSAM Status code 04 up vote 0 down vote favorite 1 I am running one COBOL pgm which is reading one VSAM file. Below is ithe input output section in my pgm. FILE-CONTROL. SELECT INPUT-FILE ASSIGN TO DDINPUT ORGANIZATION IS INDEXED ACCESS MODE IS RANDOM RECORD KEY IS INPUT-KEY FILE STATUS IS WS-INPUT-STATUS. and FD entry is as follow. FILE SECTION. FD INPUT-FILE IS EXTERNAL (as this is in sub pgm) COPY INPUTREC. When I ran this pgm, it failed with file status code =04. Somewhere I found that when in FD we have only one record even if the file is VB it treats it is FB. So FB should have record contains or Varying clause. When I updated my FD to. FILE SECTION. FD INPUT-FILE IS EXTERNAL RECORD VARYING IN SIZE FROM 1 TO 215. COPY INPLAYOUT. job ran fine. I have one doubt Can I specify this Varying clause to maximum length, like if I write this as eg RECORD VARYING IN SIZE FROM 1 TO 2500. then will it cause any issue? cobol mainframe jcl share|improve this question edited Sep 19 '11 at 6:39 asked Sep 7 '11 at 10:08 Saisha 32231126 add a comment| 2 Answers 2 active oldest votes up vote 4 down vote accepted Assuming your VSAM file is properly initialized and your JCL is coded consistently with your program requirements there should be no issue. The VARYING clause is simply telling COBOL to reserve enough space in the b