Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Work file not open ISPF102

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> TSO/ISPF
View previous topic :: :: View next topic  
Author Message
sureshbabuamara

New User


Joined: 20 Sep 2007
Posts: 16
Location: India

PostPosted: Wed Nov 07, 2007 6:01 pm    Post subject: Work file not open ISPF102
Reply with quote

Hi,

I am trying to invoke a Skel using REXX program. But i am getting this below erorr

Code:

ISPF system data set allocation error - press Enter to continue.
Temporary control card data set cannot be allocated.           
DAIR RC = 12 dec, DARC = 9700 hex.                             
***


Code:

                               ISPF Dialog Error                               
 Command ===>                                                                 
                                                                               
 ******************************************************************************
 * ISPF102                                                                    *
 *                                                                            *
 * No work file                                                               *
 * Work file not open.                                                        *
 *                                                                            *
 *                                                                            *
 *                                                                            *
 *                                                                            *
 *                                                                            *
 *                                                                            *
 * Current dialog statement:                                                  *
 * ISPEXEC FTOPEN TEMP                                                        *
 *                                                                            *
 * Enter HELP command for further information regarding this error.           *
 * Press ENTER key to terminate the dialog.                                   *
 *                                                                            *
 *                                                                            *
 *                                                                            *
 *                                                                            *
 ******************************************************************************


IF found this problem after my REXX program terminated intermediately in the previous run.

When I try this with other TSOid I didnt get this error. Because of this error I am unable to proceed further.

Kindly let me know how to over come this error or provide me the LINK where I can get soloution.

Thanks and Regards,
Suresh,
India.
Back to top
View user's profile Send private message

enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10231
Location: italy

PostPosted: Wed Nov 07, 2007 6:43 pm    Post subject: Reply to: Work file not open ISPF102
Reply with quote

This things usually happen during the development stages where not all
the return codes are tested and acted upon

an ftopen error will yeld a return code of 8 and I checked the behavior with this simple rexx

Code:

/*REXX - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - */
trace "r"                                                             
address ispexec "FTOPEN TEMP"                                         
if  RC = 8 then,                                 
    address ispexec "FTCLOSE"                                         
return                                                                                                                                         

a file tailoring is left hanging but no abend indicators
running it it will flip/flop between the two states ( complete/interrupted)

I would rather check how the ISPF work/temporary files are allocated,
they sometimes cause this kind of weird results
a logon logoff will certainly fix everything

this is the test used to find the name of the temprary dataset allocated
Code:

/*REXX - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - */
trace "r"                                                             
address ispexec "FTOPEN TEMP"                                         
if  RC = 8 then do                                                     
    address ispexec "FTCLOSE"                                         
    return                                                             
end                                                                   
address ispexec "FTCLOSE"                                             
address ispexec "VGET ZTEMPF"                                         
say "ZTEMPF" ztempf                                                   
return 0                                                               
Back to top
View user's profile Send private message
sureshbabuamara

New User


Joined: 20 Sep 2007
Posts: 16
Location: India

PostPosted: Thu Nov 08, 2007 9:50 am    Post subject:
Reply with quote

I tried logging off and logging in again. But it is still giving the same problem. It is saying like ispf saying allocation error. Please let me know wat could be the solution for this?
Back to top
View user's profile Send private message
enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10231
Location: italy

PostPosted: Thu Nov 08, 2007 12:16 pm    Post subject: Reply to: Work file not open ISPF102
Reply with quote

after a little bit of scrambling thru the manuals
here is the meaning of :
dair(12) ded and darc(9700) hex
dair 12 dynalloc error due to sms

darc 9700 here is the description
Quote:
9700
Meaning: Severe storage management subsystem (SMS) IDAX error.

Application Programmer Action: Check field S99ERSN for a
non-zero value. A non-zero value in S99ERSN is a reason code.
See "SMS Reason Code (S99ERSN)" in topic 26.2.1.1 for the
possible reason codes. If the system displayed message
IKJ56893I, SMS messages for the error follow IKJ56893I. If the
system displayed message IKJ56894I, no messages were returned.
Request the message processing option of dynamic allocation to
obtain related messages and resubmit the request. If you still
cannot obtain messages, contact your system programmer for
assistance.

Corresponding Messages: IKJ56893I (messages were displayed) or
IKJ56894I (messages not displayed).


have somebody chek the system log for the ikj messages quoted
and take the actions suggested

another lazy way of proceeding without reading
would be to from ispf option 3.4
get a list of thedataset with Your high level qualifier
and delete the ispf work files ( just put a d in front of them )
those in use will not be deleted
Back to top
View user's profile Send private message
sureshbabuamara

New User


Joined: 20 Sep 2007
Posts: 16
Location: India

PostPosted: Mon Nov 12, 2007 4:23 pm    Post subject:
Reply with quote

Hi e.s,

My TEMP file naming convention is "Userid.SYS51UN.SPFTEMP*.CNTL". As you said I have deleted all Files related to this and logged off and logged in but still I am getting the same error message.

After reading some online papers I found this *.*.SPFTEMPn.CNTL will created by ISPF automatically when ever an user logged in. In my case this is not happening automatically.

I have TRACED my REXX program and found that, while FTOPEN TEMP is giving RC =8, where I have not handled my REXX pgm when RC=8 and my TEMP is in shared mode that time.

Code:

'ISPEXEC FTOPEN TEMP' 
'ISPEXEC FTINCL ASBSKEL'   
'ISPEXEC FTCLOSE'     
'ISPEXEC VGET (ZTEMPF) SHARED'


Code:

   298 *-*  'ISPEXEC FTOPEN TEMP' 
       >L>    "ISPEXEC FTOPEN TEMP"
       +++ RC(20) +++                     
   299 *-*  IF RC > 0                     
       >V>    "20"                       
       >L>    "0"                         
       >O>    "1"                         
       *-*   THEN                         
       *-*   DO                           
   300 *-*    SAY 'RC' RC                 
       >L>      "RC"                     
       >V>      "20"                     
       >O>      "RC 20"                   
RC 20                                     
   301 *-*    SAY ZERRLM                 
       >V>      "Work file not open."     
Work file not open.                       
   302 *-*    SAY ZERRSM                 
       >V>      "No work file            "
No work file                             
   303 *-*   END                         


Even I have created this TEMP file manually, but still the error is persisting.
Can you suggest me how to get back this "Userid.SYS51UN.SPFTEMPn.CNTL".

Thanks,
Suresh.
Back to top
View user's profile Send private message
enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10231
Location: italy

PostPosted: Mon Nov 12, 2007 5:50 pm    Post subject: Reply to: Work file not open ISPF102
Reply with quote

what is the difference between the two tso ID' s;
You said that another id does not have the problem.

after the failure
go to SDSF select Your tso task and look at the messages.
You might get an hint whether my preceding considerations apply !!
Back to top
View user's profile Send private message
sureshbabuamara

New User


Joined: 20 Sep 2007
Posts: 16
Location: India

PostPosted: Tue Nov 13, 2007 9:08 pm    Post subject:
Reply with quote

Hi e.s,

The TSOID which I sucessfully ran is my team members only, we have similar properties.

Because I have ran this REXX program using my TSOID, I am getting this problem. I tried in my colleague after I rectified the issue in REXX program.

Now my TEMP file is not creating automatically, I have logged out & in and deleted existing TEMP files, but still the problem is persisting.


Thanks,
Suresh.
Back to top
View user's profile Send private message
sureshbabuamara

New User


Joined: 20 Sep 2007
Posts: 16
Location: India

PostPosted: Wed Nov 21, 2007 2:26 pm    Post subject:
Reply with quote

HI ALL,

The problem got rectified, when I ran REXX program my TSO PREFIX got changed to ZUSER (because i am not passing userid to zuser). I have changed the PREFIX to my ID, now its working fine.

Thanks for your help.

Regards,
Suresh Amara.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> TSO/ISPF All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Receive a file using PCOMM macro Harald.v.K IBM Tools 0 Thu Mar 23, 2017 6:50 pm
No new posts Export flat file data into excel sheet murali.andaluri DFSORT/ICETOOL 2 Mon Mar 20, 2017 5:39 pm
No new posts Formatting VB File Learncoholic DFSORT/ICETOOL 3 Mon Mar 20, 2017 12:29 pm
No new posts Updating a VSAM file with DISP=OLD sheersh JCL & VSAM 8 Tue Mar 14, 2017 6:14 pm
No new posts SORT VSAM file with each field one by... maxsubrat DFSORT/ICETOOL 6 Tue Mar 14, 2017 1:07 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us