>> IT is not a regimented 9-5 job.
>> Never was.
>> Never will be!
>Wanna bet?? :-(
I'm not sure what you mean.
It will always be more.
When in doubt.
PANIC!!
--
For IBM-MAIN subscribe / signoff / archive access instructio
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of Ted MacNEIL
>
> [ snip ]
>
> IT is not a regimented 9-5 job.
> Never was.
> Never will be!
Wanna bet?? :-(
-jc-
--
For IBM-MAIN subscribe / s
>So, we can deduce, Watson, that they either have no coverage for lunch hour (a
>management problem: too few operators scheduled for their needs) or an
>employee who doesn't care about the job and leaves without handing off to
>someone else (a personnel problem).
I have worked for two unionise
Using tape for logging wouldn't have cause the OP's problem if their shop
were using virtual tape or an automated cartridge system, instead of the
biological tape mounting facility.
Technologically speaking, they hit some area of MQ logging that was
serialized while waiting on a tape mount; bu
The better way to log is to use disk. Anybody using tape logging is just
asking for it. And, as I mentioned earlier, with a little work, the disk
logs can be copied to tape (note: the BSDS needs to be modified to reflect
the tape volsers) for D/R purposes.
On Tue, 15 Aug 2006 19:54:01 +0530, Jacky Bright <[EMAIL PROTECTED]>
wrote:
> Hi,
>
>I faced prob. in production today ... We got error at around 12.20 that MQ
2
>of 8 active logs full.
>
>Thereafter, operator had replied the message and the console was asking to
>mount tape in 780 tape drive. H
Hi,
I faced prob. in production today ... We got error at around 12.20 that MQ 2
of 8 active logs full.
Thereafter, operator had replied the message and the console was asking to
mount tape in 780 tape drive. However operator kept the message un-attended
and left for lunch.
Later application pp
richard ...
but how to justify this ..if u have 6 pending logs then why question of
logs being full...
When logs are being offloaded .. then system should write logs to remaining
log datasets which didn't happen ??
On 8/15/06, Richard Tsujimoto <[EMAIL PROTECTED]> wrote:
Jacky,
I suspec
Jacky,
I suspect MQ was trying to capture critical logging info and needed to
ensure the integrity of the data, causing a *freeze* of the environment.
It doesn't matter how many logging tapes are available during this period
if MQ is unable to safestore this data.
I would suggest changing the
Hi,
I faced prob. in production today ... We got error at around 12.20 that MQ
2 of 8 active logs full.
Thereafter, operator had replied the message and the console was asking to
mount tape in 780 tape drive. However operator kept the message un-attended
and left for lunch.
Later application
Hi,
I faced prob. in production today ... We got error at around 12.20 that MQ 2
of 8 active logs full.
Thereafter, operator had replied the message and the console was asking to
mount tape in 780 tape drive. However operator kept the message un-attended
and left for lunch.
Later application pp
11 matches
Mail list logo
