VSAM Compression Mgmt Error During Expansion RC=20

BETH BEGGS · New User Joined: 02 Feb 2006 Posts: 5

I am getting this message in our CICS partition. REASON code is 2181. Message text says processing cannot continue because storage cannot be obtained for the LZ-tree. Do I need to increase partition GETVIS? Or, do I need to do something else. Any help appreciated. IBM manuals give very little information!

William Thompson · Posted: Tue Feb 06, 2007 1:54 am

Is ther a DFH (or other) error message number anywhere?

BETH BEGGS · New User Joined: 02 Feb 2006 Posts: 5

The error message number 4A90I, points to VSAM, and the error is apparently issued by module IKQCSCZL. The message is also described as RS_TREE_GET_FAILED. That's as far as I've been able to take it. I appreciate any help !!!

William Thompson · Posted: Tue Feb 06, 2007 6:34 pm

4A90I?

BETH BEGGS · New User Joined: 02 Feb 2006 Posts: 5

Yes, it is 4A90I. I found reference to this message in IBM documentation for VSAM. We are running z/VSE under z/VM on an IBM mainframe.

BETH BEGGS · New User Joined: 02 Feb 2006 Posts: 5

If this helps, this is where I found the information within IBM's website --

Title: VSE Central Functions V6R3 VSE/VSAM Logic DRM
Document Number: SC33-6321-00

Chapter 6.13 Compression Management Reason and Return Coes
6.13.5 Reason Codes for RC=20

I found very similar text in another IBM manual in which the error 4A90I was specifically referenced. The explanation was fundamentally the same as in the documentation I reference here.

William Thompson · Posted: Tue Feb 06, 2007 7:41 pm

Beth,

Found APAR with that message, has no bearing but as a sideways pointer:

BETH BEGGS · New User Joined: 02 Feb 2006 Posts: 5

I am awaiting all needed signatures (G* bless the auditors!) so I can implement this fix. We are increasing both the CICS partition allocation and the system GETVIS in the VSE guest in question. This was a sporadic problem, so it may be some time before we consider it closed. Thanks for your help, and we'll work on the "no-news-is-good-news" theory. With regards.......

aparnapaj · New User Joined: 09 Jun 2007 Posts: 1 Location: hyderabad

Hi..

I too got the same error recently(in VSE).

The problem was the usage of a CLASS which can handle smaller jobs (which was unable to expand the large files) and so when i changed the CLASS and tried out, the job was running fine and the problem was resolved.

Hope this may be useful and help out u and u can try the same to rectify this error.

dick scherrer · Posted: Fri Oct 24, 2008 4:33 am

Hello and welcome to the forums,

Thank you for the info

The "new" class is probably for a larger partition which solved the memory shortage.

Please note that this topic has been inactive for over one and a half years, so a reply from the original participants is not so likely (unless Bill is watching. . .).