IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

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


IBM Mainframe Forums -> CICS
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
hcl_ln

New User


Joined: 14 Sep 2005
Posts: 21

PostPosted: Fri Jul 20, 2007 2:19 am
Reply with quote

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?
Back to top
View user's profile Send private message
William Thompson

Global Moderator


Joined: 18 Nov 2006
Posts: 3156
Location: Tucson AZ

PostPosted: Fri Jul 20, 2007 3:20 am
Reply with quote

hcl_ln wrote:
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"
That is a good one....ACST (as a CICS abend, is not found) and S064 does not make sense (even with R001)...
Based upon what you've posted, some other entity (other than z/OS or CICS) is involved....
Is there any other information you can provide?
Back to top
View user's profile Send private message
Earl

Active User


Joined: 17 Jun 2007
Posts: 148
Location: oklahoma

PostPosted: Fri Jul 20, 2007 3:27 am
Reply with quote

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 ?
Back to top
View user's profile Send private message
hcl_ln

New User


Joined: 14 Sep 2005
Posts: 21

PostPosted: Fri Jul 20, 2007 6:37 pm
Reply with quote

Thank you for the replies.

I can see these messages in the CICS dump from the held queue.
Back to top
View user's profile Send private message
Earl

Active User


Joined: 17 Jun 2007
Posts: 148
Location: oklahoma

PostPosted: Fri Jul 20, 2007 6:47 pm
Reply with quote

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
Back to top
View user's profile Send private message
shagnwrx

New User


Joined: 07 Jul 2006
Posts: 17
Location: Birmingham, AL

PostPosted: Sat Jul 21, 2007 12:01 am
Reply with quote

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.
Back to top
View user's profile Send private message
Earl

Active User


Joined: 17 Jun 2007
Posts: 148
Location: oklahoma

PostPosted: Sat Jul 21, 2007 12:34 am
Reply with quote

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
Back to top
View user's profile Send private message
shagnwrx

New User


Joined: 07 Jul 2006
Posts: 17
Location: Birmingham, AL

PostPosted: Sat Jul 21, 2007 12:46 am
Reply with quote

Earl wrote:
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



He actually indicated he got the same messages when he used CEMT S FI(filename) commands. I have a sneaky suspicion that this is a third party file manipulation system not unlike AFCS. The messages are not CICS nor z/OS messages.

Also sounds like he's finding the ACST messages in another sysout other than the JESLOG/SYSLOG for the CICS region. The JESLOG will have all the needed info (As long as the DFHFCnnnn messages are not suppressed by whatever product is being used).
Back to top
View user's profile Send private message
Earl

Active User


Joined: 17 Jun 2007
Posts: 148
Location: oklahoma

PostPosted: Sat Jul 21, 2007 12:52 am
Reply with quote

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 ?
Back to top
View user's profile Send private message
shagnwrx

New User


Joined: 07 Jul 2006
Posts: 17
Location: Birmingham, AL

PostPosted: Sat Jul 21, 2007 1:35 am
Reply with quote

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


Actually, there are quite a few products and interfaces out there that intercept error messages, then format their own. However, The real CICS or z/OS messages are usually buried in the syslog somewhere. Just a matter of finding them.
Back to top
View user's profile Send private message
Earl

Active User


Joined: 17 Jun 2007
Posts: 148
Location: oklahoma

PostPosted: Sat Jul 21, 2007 1:52 am
Reply with quote

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.
Back to top
View user's profile Send private message
shagnwrx

New User


Joined: 07 Jul 2006
Posts: 17
Location: Birmingham, AL

PostPosted: Sat Jul 21, 2007 2:49 am
Reply with quote

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.

Code:

S FI(TESTEV) OPE ENA                                                         
STATUS:  RESULTS - OVERTYPE TO MODIFY                                         
 Fil(TESTEV  ) Vsa Clo Une Rea                 Sha       OPEN/CLOSE FAILED
        Dsn( MI05P.NON.EXISTENT.DSN                       )   


So this is what OP initially sees. Nothing really to go on here.

However, if we go check the JESLOG for the cics region we DO see the DFHFCnnnn messages:

Code:

+DFHFC0952 ADZCICS  635                                                       
   DYNAMIC ALLOCATION OF NON-RLS FILE TESTEV FAILED. RETURN CODE               
 X'0004',X'1708' IN MODULE DFHFCFS.


This is why I think OP is not looking at the jeslog. His messages (ACTS) are probably from some random sysout on the region.
Back to top
View user's profile Send private message
Earl

Active User


Joined: 17 Jun 2007
Posts: 148
Location: oklahoma

PostPosted: Sat Jul 21, 2007 3:10 am
Reply with quote

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.
Back to top
View user's profile Send private message
shagnwrx

New User


Joined: 07 Jul 2006
Posts: 17
Location: Birmingham, AL

PostPosted: Sat Jul 21, 2007 3:19 am
Reply with quote

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.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> CICS

 


Similar Topics
Topic Forum Replies
No new posts MacKinney Batch to CICS upgrade causi... CICS 7
No new posts IEW2315E 1369 Link error All Other Mainframe Topics 3
No new posts Unable to interpret a hex value to De... COBOL Programming 7
No new posts Help on IMS -API URL migrating from P... IMS DB/DC 1
No new posts Associating a USERID with a CICS-Libe... CICS 0
Search our Forums:

Back to Top