Looking at this from a slightly different
angle for a moment :-
We have RACF as our ESM and it is set
to automatically revoke a user after 180 days of inactivity. Without discussing
if this is a good rule (or duration), it does raise an interesting issue.
If our system stays up for more than
I had the luxury of having the password expiration time set to match the
existing MVS times. The removal of expired users was triggered by a once a
year userid reconcilliation. But still lots of expired userids were allowed
to remain. The threat of having to pay for disk space never materialized.
We use VM:Secure to manage our user directory. We sweep our user directory
every year or so to look for inactive userids. We keep system service
machines under a special directory manager so they are not involved in the
sweeps. There are other sensitive userids that are kept under other
directory
Many thanks to all who replied. I have been able to reformat the disk
and remove the file.
PVM protocol documentation found.
David Boyes [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Don't know whether anyone else may ever need this, but FYI: Appendix 1 of
the PVM Admin and Operation manual does document the buffer layout and
sequence of events for PVM link communications.
We're (pretty urgently) looking for a replacement product for one which
just suffered hardware failure. It's unlikely that it can be resurrected
- very old hardware.
Requirements:
- Batch file transfers between VM and z/OS (initiated either by a VM:Batch
job or a z/OS batch job), performed
Mike,
Connect: Direct from Sterling Commerce meets most of your requirements.
It doesn't work with SFS, though. Transfers to VM can go to minidisk or
reader. Transfers from VM come from minidisk.
Dennis O'Brien
An appeaser is one who feeds
Mike,
What was the software product that suffered a hardware failure ...
and how were they related? Do you mean something like COM-10 or 3745
over VTAM replacement?
JR Imler
JR (Steven) Imler
Computer Associates
Senior Software Engineer
Work: +1 703 708 3479
Fax: +1 703 708 3267
[EMAIL
I didn't want to mention it so that we would not get side-tracked on that
particular product, but it was Network Systems DX Series hardware that
died.
It is tightly tied to their NETEX and BFX software.
Dennis' suggestion of Sterling's Connect:Direct seems fraught with future
problems. Didn't
It does work with SFS to and from SFS. See setting up the CDVMSFS
machine and use SFSDIR in your copy statements.
Yes, it does require VSAM. ISPF and VTAM too. And the Secure+ version
of it is not supported on VM. Sigh.
Marcy Cortes
This message may contain confidential and/or privileged
Unfortunately I don't know much about it's capabilities, but what about
XCOM from CA?
Mike Walter wrote:
We're (pretty urgently) looking for a replacement product for one which
just suffered hardware failure. It's unlikely that it can be resurrected
- very old hardware.
Requirements:
-
11 matches
Mail list logo
