RE:     Data queue's


For data queues and other objects that need complicated or non-retreivable
(DSPxxx) information for their creation  I generally create
a CL program to create them. Things like complicated PGMs that need over
rides.   Even things like adding or removing Trigger programs from 50+ 
files.   By creating a CL program to Create, Addpftrg, Rmvpftrg or whatever
you can quickly respond to an emergency.  In that scenerio its nice just
have a program operations can call(at 2am !!)  and know it's done right.   

We have a CL that creates each Data Queue that is used in production. 
Also a CL program that Adds and Removes triggers from production files
just for emergencies.  (try displaying the length of a Data Queue!!)

It may be the hard way, but it works and the person(the Operator!!) doesn't
have to know the parameters or have to get them right.

John Carr

Jeff Said
>We recently had a problem htat caused us to bring our 530 down with sbs
>active (had a job that would not end).  When the system came up, several
>dtaq were damaged.  In trying to recreate these dtaq (which had
>duplicates in other libraries on the system and on our development box),
>I discovered that retrieving all the needed parameters was impossible,
>as was copying a dtaq (although I could save & restore, which is what I
>ended up doing).
>Is there a way to see all the parameters of a dtaq (e.g. TYPE *STD or
>I did try the usrtool DSPDTAQ, but that didn't seem to show all of them.
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "".
| To unsubscribe from this list send email to
| Questions should be directed to the list owner/operator:

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].