Hello,
Lately I installed a PTF to EREP on second level z/VM. I'm looking for a
way to test the PTF. Do you know how to simulate hardware error and force
EREP to write records ?
So far I tried...
- writing to the file simultaneously by 2 users.
- attempt to write on read-only mdi
Automations is handled by another group. Their response is:
CAOPER is configured to be the OBSERVER.
OPERATOR terminates CAOPER's OBSERVER then initiates SECUSER for itself. When
automation routine is done, OPERATOR terminates its own SECUSER and sets CAOPER
back to OBSERVER.
Thanks
Joe
Joseph,
Looks like you got OPERATOR and CAOPER (both z/VM userids, nothing to with
Linux), competing over being the SECUSER of your Linux server.
Do you have CA Operator running in both userids and both being configured
to monitor the Linux console?
Ronald van der Laan
Op dinsdag 27 september 20
Thanks. I see serial-getty@ttyS0 is the issue. Will try it.
Thanks
Joe
Technology Services Group
Mainframe Operating Systems
Pershing Plaza
95 Christopher Columbus Drive
Floor 14
Jersey City, N.J. 07302
Work 201-395-1509
Cell917-903-0102
-Original Message-
From: Linu
On 09/28/2016 05:22 PM, Richard Plangger wrote:
> Hi,
>
> I'm working on pypy s390x port and I'm currently evaluating the vector
> instructions. I have one virtual machine access in marist.edu.
>
> The vector optimization for PyPy do not show very good speedup for
> s390x. This is strange, becaus
Hi Vitale.
His work for me on RedHat 7:
ExecStart=-/sbin/agetty --autologin root -s %I
Copy and Paste on your linux.
ln -s /etc/systemd/system/serial-getty@ttyS0.service
/etc/systemd/system/getty.target.wants/
and start device:
systemctl daemon-reload
systemctl start serial-getty@ttyS0
Is there a minus '-' after ExecStart:ExecStart=-/sbin/agetty --autologin
root -s ℅l
Thanks
Joe
Technology Services Group
Mainframe Operating Systems
Pershing Plaza
95 Christopher Columbus Drive
Floor 14
Jersey City, N.J. 07302
Work 201-395-1509
Cell917-903-0102
-Orig
