What can cause a 3523 ABEND in VISION:Inform?

Document ID:  TEC535031
Last Modified Date:  08/03/2015
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA VISION:Inform for CICS
  • CA VISION:Inform for z/OS

Releases

  • CA VISION:Inform for CICS:Release:4.0
  • CA VISION:Inform for z/OS:Release:4.0

Components

  • VISION:Inform:V:INFM

Description:

The Messages Manual explains that a 3523 ABEND indicates insufficient space in the Foreground Library or Communication File. The questions are : How do you tell which file? And how do you resolve the problem?

Solution:

When a 3523 ABEND occurs, you can tell which file has run out of space by noting the attempted action.

If it is an activity that catalogs items to the Foreground Library such as a SAVE of a query, or any of the batch jobs that copy definition elements to the Foreground Library, that is the file we need to address.

If it is an activity, that writes to the Communication File such as SUBMIT or a background processor run, that is writing a query output such as a report, then that is the culprit.

If it is the Communication File, purging old reports can help, but only if you can purge many, or they are very large. This produces minimal gain as you are leaving fragmented space, so should only be used for possible immediate relief.

For either file, it is possible the problem is just fragmentation, so a backup and restore may resolve the problem if this has not been done in a long while. Otherwise the file needs to be increased. For detailed steps on increasing either file see the VISION:Inform 4.0 Installation Manual, page 5-28 for CICS or page 5-25 for IMS, "Changing the Size of the Foreground Library or Communication File". If just backing up and restoring, you can omit steps 3 and 4.

If the file is increased be sure to modify the QFILE macro in the PARMBLK source that was last used at your site. This ensures you will maintain any other parameter customizations that have been implemented at your site.

==============
  CICS users 
============== 
If the library is increased and a non-default prefix is used, the TRANSFER step becomes mandatory and it is important to note 
the comments at the top of the TRANSFER job regarding the ZAPOUT dataset: //* MEMBER TRANSFER //********************************************************************* //* THIS PROCEDURE COPIES THE LOAD MODULES NEEDED BY THE CICS ONLINE * //* SYSTEM FROM THE INSTALL LOADLIB TO THE ONLINE LOADLIB (DFHRPL). * //* THE OUTPUT LOAD MODULES ARE RENAMED USING THE SUPPLIED PREFIX. * //* * //* ***NOTE*** IF A PREFIX OTHER THAN THE DEFAULT OF 'INFORM' IS * //* USED, PLEASE REFER TO THE INSTALLATION MANUAL * //* SECTION ON THE TRANSFER JOB FOR DETAILS ON THE USE * //* "ZAPOUT" DATASET CREATED BY THIS PROCEDURE. * //* FAILURE TO RUN THE ZAP PRODUCED BY THE TRANSFER * //* UTILITY WHEN THE DEFAULT PREFIX IS CHANGED WILL RESULT * //* IN A "PROGRAM NOT FOUND" CONDITION WHEN THE CICS * //* TRANSACTION IS EXECUTED. * //*********************************************************************

Reference is to the VISION:Inform for CICS Installation Manual page 3-17:

Renaming Modules with the TRANSFER Job

Note: If the online modules are renamed, TRANSFER creates a file of IBM SUPERZAP control statements when it is executed and it is your responsibility to run the ZAP program using this file as input to the IBM ZAP program (therefore, if you have changed the delivered six-character prefix of the online modules, you must run the ZAP program). Run the ZAP against any library to which the installation load library modules are copied.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >