Skip to main content

[Migrated content. Thread originally posted on 03 August 2011]

Every few weeks our system hangs and does not allow users to login to CICS. The console is filled with messages:

JES000011E Batch spool file error; status start

These messages appear for no apparent reason as they often occur in the middle of the night when no users are using the system. In our environment, once the user enters his userid/password, control is passed to a local signon program that reads a VSAM file looking for a user record; if the record is found, it allows signon to complete. If not found, it returns "User is not set up for this CICS". When we start receiving the bathc spool error messages, the read of the VSAM file apparently fails as it appears that none of our users are in the VSAM file. Once I bounce the region, everyone can sign in again. Would someone give me a clue as to how to determine the cause of this error? And what exactly is a batch spool file error anyway? The MF doc isn't very explicit.

[Migrated content. Thread originally posted on 03 August 2011]

Every few weeks our system hangs and does not allow users to login to CICS. The console is filled with messages:

JES000011E Batch spool file error; status start

These messages appear for no apparent reason as they often occur in the middle of the night when no users are using the system. In our environment, once the user enters his userid/password, control is passed to a local signon program that reads a VSAM file looking for a user record; if the record is found, it allows signon to complete. If not found, it returns "User is not set up for this CICS". When we start receiving the bathc spool error messages, the read of the VSAM file apparently fails as it appears that none of our users are in the VSAM file. Once I bounce the region, everyone can sign in again. Would someone give me a clue as to how to determine the cause of this error? And what exactly is a batch spool file error anyway? The MF doc isn't very explicit.
My initial guess would be that something is failing further down in the file I/O stack, and the batch spool file errors and your login program errors are both symptoms of that. If you're using Fileshare for those files, I'd suspect a problem with the Fileshare server or with network comms; if you're using regular file I/O, a file descriptor/handle leak is one possibility.

Something like this needs proper investigation, which means opening an incident with Micro Focus and working with Customer Care to get a proper data collection.

[Migrated content. Thread originally posted on 03 August 2011]

Every few weeks our system hangs and does not allow users to login to CICS. The console is filled with messages:

JES000011E Batch spool file error; status start

These messages appear for no apparent reason as they often occur in the middle of the night when no users are using the system. In our environment, once the user enters his userid/password, control is passed to a local signon program that reads a VSAM file looking for a user record; if the record is found, it allows signon to complete. If not found, it returns "User is not set up for this CICS". When we start receiving the bathc spool error messages, the read of the VSAM file apparently fails as it appears that none of our users are in the VSAM file. Once I bounce the region, everyone can sign in again. Would someone give me a clue as to how to determine the cause of this error? And what exactly is a batch spool file error anyway? The MF doc isn't very explicit.
Thanks, I will have to do that. I am running into another problem this week where the system hangs for no apparent reason. I cannot access the groups from the enterprise admin console; it shows I/O errors. I am beginning to wonder if there are indeed file share issues.

[Migrated content. Thread originally posted on 03 August 2011]

Every few weeks our system hangs and does not allow users to login to CICS. The console is filled with messages:

JES000011E Batch spool file error; status start

These messages appear for no apparent reason as they often occur in the middle of the night when no users are using the system. In our environment, once the user enters his userid/password, control is passed to a local signon program that reads a VSAM file looking for a user record; if the record is found, it allows signon to complete. If not found, it returns "User is not set up for this CICS". When we start receiving the bathc spool error messages, the read of the VSAM file apparently fails as it appears that none of our users are in the VSAM file. Once I bounce the region, everyone can sign in again. Would someone give me a clue as to how to determine the cause of this error? And what exactly is a batch spool file error anyway? The MF doc isn't very explicit.
Thanks, I will have to do that. I am running into another problem this week where the system hangs for no apparent reason. I cannot access the groups from the enterprise admin console; it shows I/O errors. I am beginning to wonder if there are indeed file share issues.
Terms & ConditionsAccessibility statement