|
deutsch
Headlines
l
Easy Dataset Cleanup using EQQDELDS
l
Tricky Planniong
Rules with 'TWS for z/OS'
l
Migration
without Event Loss
l
An
Automatic Tracker Migration during IPL and a following Test Procedure
l
Logic within
a Sort saves Effort in Programming
l
TWS for
z/OS Web Interface
Easy Dataset Cleanup using EQQDELDS
June
2004 - Preventative cleanup that you can perform before a job runs. This type
of cleanup does a general cleanup of data sets, which is useful if you do not know the exact state of the data sets. If you prefer to clean
up before a job first runs, look at the member EQQDELDS in the supplied sample library. This describes a program that deletes data
sets with the NEW disposition that are not referenced with a different disposition (OLD or SHR) in previous job steps. EQQDELDS is a sample program that is not part of the product, but you can use it if you
prefer this solution.
EQQDELDS supports these types of delete processing:
-
DASD data sets on primary volume(s) are deleted using IDCAMS.
-
Tape data sets are deleted using IDCAMS NOSCRATCH.
- This does not cause mount requests for the specified tape volumes.
-
DFHSM-migrated data sets are deleted using the ARCHDEL (ARCGIVER) interface.
- Data sets are not moved to primary volumes (recalled) before deletion.
(Source:
IBM Publications EQQTCT10 and EQQTMG00)
Tricky
Planning Rules with 'TWS for z/OS'
September 2003 - It seems to
be impossible to
solve some difficult planning problems? Smart technical solutions may not
be practicable? After all, standard solutions will be used to realize
workarounds to the goal - and maybe this kind of solutions are not
easy to understand and may they hold the risk to fail because of a future
calendar constellation.
A sample task shows, which tricks may be used to solve such heavy
challenges:
Sample:
An application should not be planned after a free
day (maybe at this day there is no input data available).
The trick:
Use a cyclic period as follows:
Interval: 1 / Type: W (a daily period)
and define the runcycle:
Period / Type 'N' / Free day rule 'E' / Offset '2'
and you will get the wanted result, the
application will not be planned at a Monday or a day after another free
day (holiday). The secret resides in a deviation, achieved by using a offet greater than the cycle of the period.
This sample works only with a free day rule 'E'. Use your fantasy and test more!
Top
Migration
without Event Loss
April 2003 -
Sometimes
you are not able to migrate
OPC in a timeframe without any production. In this case, there are two
different ways to loose events during the migration. At first the
migration of a tracker system together with a controller system will loose
all temporary stored events in the Common System Area (CSA), because they
are deleted by the BUILDSSX keyword, which creates a new empty CSA.
Prevent this problem by an early tracker migration (preferably
with an IPL).
The second problem is the controller migration. During this procedure a
new checkpoint dataset must be created (a stringent condition). This new
checkpoint contains no information about the pre-migration processed
events. For this reason important events may be lost during the migration
time. An easy technical solution for this ckeckpoint problem is to merge
the information of the new allocated checkpoint and records from the old
checkpoint file (previous release).
This new checkpoint file now contains all informations for a smooth and
lossless processing.
This solution has been integrated into the official users
guide.
Sample:
REPRO IFILE(CKPT) OFILE(CKPTNEW) COUNT(1)
REPRO IFILE(CKPTOLD) OFILE(CKPTNEW) SKIP(1)
Top
An
Automatic Tracker Migration during IPL and a following Test Procedure
April 2003 - The main reason which leads us to process
tracker migrations automatically, was the amount of systems we had to
process
and the high risk to loose events during a normal migration. The
change-over of a tracker system may be done automatically during a standard
IPL. The trackers on a controller system or a backup controller system must
be migrated before a controller migration, otherwise you have to migrate
the trackers together with a controller migration (linklist) and events may
be lost during this process. The migration of other trackers is not
dependend on a controller migration.
After a successfully tracker start a job will be started by automation which
processes a bundle of OPC-Commands and causes several events. A following
REXX procedure will analyse the event datasets and cause a positive test
end if all events are available.
Here You will find a technical
description.
Top
Logic
within a Sort saves effort in Programming
April 2003 - Using the not well known SORT control statement
NOMATCH -
useful in the keywords INREC and OUREC - you can get boolean logic in your
sort by an easy way.
Test the sampleob.
Top
TWS
for z/OS Web Interface
January 2003 - It is now possible to keep your eyes on your whole
batch production from anywhere in the world using our 'focal point of
view' for OPC. No software installation on a client is needed,
except there is no web browser on that workstation.
The software runs on a central mainframe system and collects all needed OPC
data building HTML files. The connection between this files and the browser
is realized by IBM's websever function MVSDS. We have several views, as there
is a
error
list table, a general information about the
current plan, a historical
view based on yearly
data and view on applications, operations,
jobs and applications added by ETT
(Event Triggered Tracking).
The sample frontend is designed on customer's needs (system names and
amounts, owner fields and so on) , we are able to customize the kind of
data and the frontend design for your special needs and wishes.
An older ISPF version of this tool is also available with all known TSO and
ISPF restrictions - but easy to install, because no z/OS Web-Server is
needed.
Top
|