Skip to main content

Error message: File Status of 9/041 is issued for Catalog, Casspool or Mvsspl02 files

  • August 20, 2013
  • 1 reply
  • 0 views

 This error can manifest itself in several forms. Sometimes, error message ' JES000011E Batch Spool File Error; Status Start  9/041 ' is written to the Console.Log file. At times the error message ' Catalog I/O error on GU status: 9/041 Retcode: 9902 ' will be seen when trying to view a Spool file. The return code of 9902 has this meaning:
   9902   Bad File status on Catalog access - Index corrupted
The error may be related to any of the three files that are used to track user datasets, Spool files and job output files such as SYSOUT and SYSPRINT. The best steps to take are to use the command line Rebuild Utility with the -n then -f options to first display the file's information then to validate the indexed structure. If either of these outputs show a problem exists in any of the three files, Catalog.Dat, Casspool.Dat or Mvsspl02.Dat, then a rebuild of the file(s) needs to happen.
 
 In order to rebuild the file(s), make a backup copy of it and then move it to a test directory. Using the Rebuild Utility, from a Micro Focus Command Line run the REBUILD command with the -p option. For other options available, such as displaying records counts or displaying processing information while the utility runs, reference the Help.
 
 There can be several causes for this error. We have had reports of a corrupted catalog, a hard drive crash causing some physical files to be missing, or a printer that became unavailable for some reason and while we made a catalog entry for the printer spool file the printer was not available resulting in a mismatch between our catalog and spool tracking files. Also, be aware that the Spool Housekeeping utility should be ran periodically to ensure the files have proper information.


#EnterpriseDeveloper
#MFDS

1 reply

  • Author
  • Rocketeer
  • 19312 replies
  • October 24, 2018

 This error can manifest itself in several forms. Sometimes, error message ' JES000011E Batch Spool File Error; Status Start  9/041 ' is written to the Console.Log file. At times the error message ' Catalog I/O error on GU status: 9/041 Retcode: 9902 ' will be seen when trying to view a Spool file. The return code of 9902 has this meaning:
   9902   Bad File status on Catalog access - Index corrupted
The error may be related to any of the three files that are used to track user datasets, Spool files and job output files such as SYSOUT and SYSPRINT. The best steps to take are to use the command line Rebuild Utility with the -n then -f options to first display the file's information then to validate the indexed structure. If either of these outputs show a problem exists in any of the three files, Catalog.Dat, Casspool.Dat or Mvsspl02.Dat, then a rebuild of the file(s) needs to happen.
 
 In order to rebuild the file(s), make a backup copy of it and then move it to a test directory. Using the Rebuild Utility, from a Micro Focus Command Line run the REBUILD command with the -p option. For other options available, such as displaying records counts or displaying processing information while the utility runs, reference the Help.
 
 There can be several causes for this error. We have had reports of a corrupted catalog, a hard drive crash causing some physical files to be missing, or a printer that became unavailable for some reason and while we made a catalog entry for the printer spool file the printer was not available resulting in a mismatch between our catalog and spool tracking files. Also, be aware that the Spool Housekeeping utility should be ran periodically to ensure the files have proper information.


#EnterpriseDeveloper
#MFDS

What if the rebuild command fails? Mine keeps telling me to use the /o and /k options.  Since this is an ES catalog data file, I don't really know what to use for those options.