The physical server is up and running but the ZOS was down for some reason. Only Mr. "sysprog" can fix this issue.
By the way, the ZOS and this web forum share the same hardware, so I don't think it's a hardware problem.
Moderators: sysprog, prino, sfan, steve-myers, Tim001
sysprog wrote:Someone stopped VTAM, cause TCP/IP and TSO unavailable. It has been fixed.
Please do not stop any existing started tasks. Allowing users to issue system administration commands does not mean allowing abusing it, otherwise we have to remove these access from general public.
prino wrote:sysprog wrote:Someone stopped VTAM, cause TCP/IP and TSO unavailable. It has been fixed.
Please do not stop any existing started tasks. Allowing users to issue system administration commands does not mean allowing abusing it, otherwise we have to remove these access from general public.
Just remove the ability of users to issue admin commands, z/OS is not Windoze which can be rebooted if you screw up. Hell, in most companies most people cannot install programs willy-nilly or even change the time.
Just slap RACF protection on essential started tasks.
MikeOfNC wrote:... I hope that sysprog's admonition can be enough of a warning to us not to do stupid things. I tried logging on this morning, couldn't,
danilohg wrote:I think the lack here is the reason why this mainframe server is available to the people ,that is knowledge and research , and not to work as a playground
And also theres a log..find who did and give him a good bye !
MikeOfNC wrote:Oh, also, has anyone else recently been getting a RACF violation when they try to purge/release SDSF held output that they own?
I now only have read access to resource JES2.CANCEL.TSUOUT amd JES2.MODIFY.TSUOUT in the OPERCMDS class, but need update.
I'm guessing that ADMIN group had update access, and now does not...?
[interesting workaround: TSO command processor DELETE will still delete my jobs from JES2.]
sysprog wrote:We just re-granted UPDATE access to JES2.CANCEL.** and JES2.MODIFY.* to public. However we had to limit MVS commands to READ access to public.
prino wrote:'P' on SDSF is still not possible, see syslog for my tries of purging PRINOJOB, but purging individual JES output is possible.
vedovatto wrote:Not able to get in! Is VTAM down again?
Or the problem is that IBM is blocking my connection?
Return to Dezhi systems: Mainframe
Users browsing this forum: No registered users and 0 guests