|
View previous topic :: View next topic
|
| Author |
Message |
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
| This may sound like an odd question, but can unique RACF ID's be assigned to jobs? Currently, all batch jobs are scheduled by CA-7 and they all carry the same RACF ID as the CA-7 task. It lets us know that it's a production job, but it gives us no details about who the job belongs to. I was thinking that if groups of jobs could be given a unique RACF ID then it would be easy to correctly route incident tickets to the proper teams if they should fail. |
|
| Back to top |
|
 |
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
Yes, it can be done using SURROGATE.
I can't for the life of me recall how it was done at my last site, but it was done like that for security reasons so that no ONE job could wipe out everything in one hit.
Sorry that I can't remember much else, but at least it's a place to start. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
| Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009
Posts: 2481
Location: Netherlands, Amstelveen
|
|
|
|
In my company the jobname determined the application support group.
So incident tickets went to the proper teams. |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
| Peter, its been that way in every company I've ever worked for up until the current one. The only requirement here is that the first character be a 'P" for Production and that the last character indicate frequency (D, W, R, M, or X). Beyond that, since the developers create and support jobs instead of the Production Support team, they can use whatever they want for the rest. |
|
| Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009
Posts: 2481
Location: Netherlands, Amstelveen
|
|
|
|
| Quote: |
Peter, its been that way in every company I've ever worked for up until the current one. The only requirement here is that the first character be a 'P" for Production and that the last character indicate frequency (D, W, R, M, or X)
|
superk,
We had a construction like that too, Being the first character the frequency, and character 2, 3 the application code.
RACF looked at the application code to see if datasets, load libraries were
allowed to be allocated, users couldnt submit production jobs if the jobname didnt start with a userid and no production datasets were allocated. |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
| Back to top |
|
|
Kjeld
Active User
Joined: 15 Dec 2009
Posts: 365
Location: Denmark
|
|
|
|
It can be a good idea to distribute authorisations among different technical users, but may be not for identifying the maintenance responsible for a job.
My site has for years used TWS (OPC) information for distributing problem tickets when jobs (operations) went on error. |
|
| Back to top |
|
|
|
|
