Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 825
  • Last Modified:

Userid doesn't have access to data set

Hello there,

I'm trying to run a job on zOS mainframe.  I've created my data sets, IND$FILE'd my COBOL and run JCL etc. and I can successfully submit the job.  

The problem is that the job then sits in the input queue.  When I look at the job in sdsf I see reference to the user not having access to the data set.  

I'm not sure what to do.  i created the dataset with my userid but when I submit the job it asks me to add characters to the job.  So, if I type an A for instance, It will say myuserA doesn't have access to the dataset myuser.blah.blah

Any idea what I can do?

Obviously I don't know too much about mainframe.  

TIA!
0
ttist25
Asked:
ttist25
  • 3
  • 3
1 Solution
 
giltjrCommented:
You will not get an security violation on file access until after the job starts to run.

On z/OS TSO user-ids are limit to 7 characters.  This is so that the system can automatically add a 8th character to uniquely identify jobs.  Job names are limited to 8 characters.  

If the job is not running there are a couple of things that could be going on.

1) Do you happen to have TYPRUN=HOLD on the job card?
2) You have submitted the job in a job class (CLASS=x) that either does not exist, the initiators that are allowed to run CLASS x are drained, or they have jobs already running in them.

You need to check with somebody to see what class you should be using.

Can you copy and paste full message that says you don't have access to a file?
0
 
ttist25Author Commented:
Sure - here you go:

 20.58.29 JOB06585 ---- FRIDAY,    16 MAR 2012 ----                            
 20.58.29 JOB06585  IRR010I  USERID AJKB1    IS ASSIGNED TO THIS JOB.          
 20.58.29 JOB06585  ICH70001I AJKB1    LAST ACCESS AT 20:52:00 ON FRIDAY, MARCH
 20.58.29 JOB06585  $HASP373 AJKB1#   STARTED - INIT 48   - CLASS P - SYS SYSB  
 20.58.29 JOB06585  IEF861I FOLLOWING RESERVED DATA SET NAMES UNAVAILABLE TO AJKB1#
 20.58.29 JOB06585  IEF863I DSN = AJKB1.SOURCE.COBOL AJKB1# RC = 04            
 20.58.29 JOB06585 *IEF099I JOB AJKB1#   WAITING FOR DATA SETS
0
 
giltjrCommented:
O.K.  This is not a security violation, its a "sharing" violation.  Meaning something else has the file open and in use.

Are you by chance browsing or editing the file in TSO?

In your JCL do you have DISP=OLD or DISP=SHR on the DD statement that has DSN=AJKB1.SOURCE.COBOL?
0
Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

 
ttist25Author Commented:
DISP=SHR

When I was doing some googling I thought I read something about a bug where a backup would hold open a data set?  Could this be related to that?
0
 
ttist25Author Commented:
Thanks again Ggiltjr.  I'm thinking there was some other process holding the data set captive.  It ran fine a while ago.  

yay!
0
 
giltjrCommented:
Yes, some other process was holding the file.  The system programmers should be able to find out what next time.

As for the bug and backup.  It depends on the backup software and how it works.  It's possible, but unlikely.
0

Featured Post

Ask an Anonymous Question!

Don't feel intimidated by what you don't know. Ask your question anonymously. It's easy! Learn more and upgrade.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now