Getting the error "FILE NOT OPEN" in the CICS regi

hcl_ln · New User Joined: 14 Sep 2005 Posts: 21

Hello,

I am getting the error "FILE NOT OPEN" in the CICS region.
The log says
"ACST ERROR 16:38:34 S064 R001 ABCD0021 filename G 15 / | | | & FILE IS NOT OPEN"

I tried open/close, enable/diable command.
CEMT S FILE(*filename*)

Still the same error.
Not sure what is the issue. Can somebody throw some light on this?

William Thompson · Posted: Fri Jul 20, 2007 3:20 am

Earl · Posted: Fri Jul 20, 2007 3:27 am

ACST ERROR 16:38:34 S064 R001 ABCD0021 filename G 15 / | | | & FILE IS NOT OPEN

where do you see this message posted? could be an application program?
do you have any transactions with ACST tranid ?

hcl_ln · New User Joined: 14 Sep 2005 Posts: 21

Thank you for the replies.

I can see these messages in the CICS dump from the held queue.

Earl · Posted: Fri Jul 20, 2007 6:47 pm

if you are getting a cics dump, then you have a transaction forcing an abend.

I'm guessing it is application program problem, and your cics application
is sending the message.

CICS messageID's are always prefixed with DFHxxxxxx

shagnwrx · Posted: Sat Jul 21, 2007 12:01 am

If those ACST messages are being issued even when using CEMT commands, then they should be accompanied by DFHFCnnnnn messages.

In the Jeslog for the CICS region in question look for DFHFCnnnnn messages regarding the failing file. My guess is that you'll see DFHFCnnnn messages directly preceding or following your ACST messages.

Earl · Posted: Sat Jul 21, 2007 12:34 am

ACST ERROR 16:38:34 S064 R001 ABCD0021 filename G 15 / | | | & FILE IS NOT OPEN

I'll be greatly suprise if this is a CICS message.,,

open/enable the file with CEMT

and then see if you read the file by
using transaction CECI

shagnwrx · Posted: Sat Jul 21, 2007 12:46 am

Earl · Posted: Sat Jul 21, 2007 12:52 am

I just can't believe CEMT S FI(FILENAME) command would produce the message.

what happened to original poster ?

hcl_ln ?

you still having problem ?

shagnwrx · Posted: Sat Jul 21, 2007 1:35 am

Earl · Posted: Sat Jul 21, 2007 1:52 am

if CEMT S FI(FILENAME) OPEN ENABLE from a 3270 greenscreen terminal, should at least get some type of green screen response of success or failure.

shagnwrx · Posted: Sat Jul 21, 2007 2:49 am

Absolutely, but not a very definitive one... here I defined a non-existent file then did the CEMT S FI(dsname) OPE ENA... Here's what ya get.

Earl · Posted: Sat Jul 21, 2007 3:10 am

agreed, poster should be able to see a DFHCnnn message if the CEMT is failing.

if poster is seeing message on console syslog, the OP should be able to tell what job it is coming from.

I still would like to see the original posters' greenscreen response.

with your example, I can tell it is a vsam file, and the fully qualified dataset name MI05P.NON.EXISTENT.DSN

I would search the CICS sysout for the job, same DFHCnnn message should be there also.

next, I would research that the vsam file does exist.

shagnwrx · Posted: Sat Jul 21, 2007 3:19 am

Agreed, I used that as just an example.. The DSN truly does not exist Hence the 1708 rc in the DFHFC message. (SVC99 RC 1708 is DSN Doesn't exist).

Alot of times programmers will misspell the dsn in either the file definition or the FCT definition.. and throw the 1708's. I am kinda hoping the OP sees this and that's all his problem may be.

Either way as we both eluded to, Jeslog all the way for fixing open errors. He's probably looking at MSGUSR (CSFL/CSNE Dest) and only finding those aforementioned ACTS messages. Just a guess here.