|
View previous topic :: View next topic
|
| Author |
Message |
cvijay784
Warnings : 1
New User
Joined: 18 Jun 2008
Posts: 54
Location: Colombo
|
|
|
|
The requirement is to find a string 'SPACSECI' in JESMSGLG of all jobs those ran.
The objective of doing this is to increase the space on DASD for datasets used by jobs for I/O processing.
In this way, we can avoid SE37 abend in advance.
We search for string 'SPACSECI' manually in each & every job.
We want to make this process automated.
If anyone knows, please provide your help |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10888
Location: italy
|
|
|
|
why should we spend time providing a solution which is just plain WRONG??
for storage management You need to put in place the proper procedures
but... who writes SPACSECI in the JESMSGLG ?
not certainly zOS itself,
check that application description to find out about how and when
if the same message is shown on the console,
it would be better to scan the console LOG rather than each job |
|
| Back to top |
|
|
cvijay784
Warnings : 1
New User
Joined: 18 Jun 2008
Posts: 54
Location: Colombo
|
|
|
|
| I checked the application. SPACSECI is displayed by the system z/os in JESMSGLG. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10888
Location: italy
|
|
|
|
| Quote: |
| checked the application. SPACSECI is displayed by the system z/os in JESMSGLG. |
it tells nothing on WHO does it,
anyway zOS has nothing to do with SPACSECI being displayed
( a BMC product does it )
why don' t You check the BMC manuals to see if that message is logged somewhere else and get it from there
if You had posted the whole message found in the JESMSGLG
we would have saved lots of useless time, typing, network traffic |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8796
Location: Welsh Wales
|
|
|
|
I think that the OP wants to see which jobs have a message (from what I guess is) STOPX37.
I suppose if the message is there, then the need for intervention is deemed appropriate. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10888
Location: italy
|
|
|
|
Hi expat!
I agree with You, but had he said it 29 posts ago we would have saved
lots of valuable time 
also if I remember correctly stopx37
should write an SMF record and a message to the console
so I agree that it' s good to find out, but the ts is doing in the wrong way
processing the SMF dataset should be the first choice,
could even be done with a simple icetool job |
|
| Back to top |
|
|
cvijay784
Warnings : 1
New User
Joined: 18 Jun 2008
Posts: 54
Location: Colombo
|
|
|
|
| Yes expat. This is to stop SE37 |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
| enrico-sorichetti wrote: |
also if I remember correctly stopx37
should write an SMF record and a message to the console |
For what it's worth, our shop uses the STOPX37 product. You're correct, it writes messages to the console (SVM4***I). In automation, we trap selected SVM4* messages and write them to a log dataset. Once a month the log dataset is dumped to a report which the Storage & Media team uses to reconcile job failures that were due to storage issues. |
|
| Back to top |
|
|
cvijay784
Warnings : 1
New User
Joined: 18 Jun 2008
Posts: 54
Location: Colombo
|
|
|
|
| what is STOPX37 ? |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10888
Location: italy
|
|
|
|
the whole topic has been a shameful waste of time
and is going to be deleted shortly
all the reporting has already been done
any decent storage support group using STOPX37 should know about
the smfx37b utility that does exactly what the TS requires
Use [URL] BBCode for External Links
here is a quote from the manual
| Quote: |
The StopX37/II Analysis Program (SMFX37B) can be used to monitor
StopX37/II and its optional components. For information to be available, the
base product and the desired product option(s) must be started (refer to the
MAINVIEW SRM User Guide and Reference accompanying this product for
information on starting StopX37/II and the other optional components).
The SMFX37B program analyzes the SMF file for StopX37/II SMF records.
The report produced contains the job name, program name, job start time and
date, data set name, and action taken. There may be multiple entries for the
same job, since StopX37/II may have made several recovery attempts while
saving the job.
The user is encouraged to make this program a part of the daily SMF
processing routine. If StopX37/II has volume switched a permanent data set,
the SMFX37B program can inform your installation's DASD manager which
data sets are multivolume.
In large installations, where the amount of SMF data generated makes it
difficult to run the SMFX37B program, it is possible to change the SMF
dump program to write StopX37/II records to a separate data set. The
following job stream selects StopX37/II SMF records and writes them to a
generation data set residing on disk.
|
|
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2594
Location: Silicon Valley
|
|
|
|
If I did not have STOPX37...
I would scan the system log looking for abends, from that then determine which jobs abended, then look at the job output for the job that was identified. |
|
| Back to top |
|
|
|
|
