Hi,

Our system going down frequently. i see this message

AWSSTA081E Process ID 25016, component APSMON, has terminated
AWSSTA084I ... performing restart of process APSMON
AWSSTA081E Process ID 25017, component CPU, has terminated
AWSSTA086E ... system wide log out in progress
AWSSTA125I System shutdown in progress ...
eDMosaF0 terminating
eDMosaA0 terminating
AWSSTA121E Shutdown failed, trying forced shutdown, level 1 ...
AWSSTA122I ... waiting for process 25026, OSA
AWSSTA141E System failure

could you please let me know. why it happens frequently, what can we do to avoid it.

We have defined 2 CPUS. but system is only one CPU.

System startup messages:
When system started got the below message:
z1090, version 1-2.41.23.01, build date - 09/20/10 for Linux on SuSE 64bit

AWSSTA014I Map file name specified: ./kaprof2
AWSRAS181I 4 Snapdump incident(s), RAS trace and RAS log files occupy 351675994 bytes in /home/ibmsys1/z1090/logs
AWSRAS182I Associated files, logs and core files occupy 766681 bytes in /home/ibmsys1/z1090/logs
AWSSTA204I zPDT started in directory '/z1'.
AWSSTA146I Starting independent 1090 instance 'ibmsys1'
OSA code level = 0x4101

AWSEMI314I CPU 1 zPDTA License Obtained
AWSEMI314I CPU 0 zPDTA License Obtained
AWSDSA010I AWSOSA is ready for chpid: 0xA0 device: 0x402
AWSDSA010I AWSOSA is ready for chpid: 0xA0 device: 0x401
AWSDSA010I AWSOSA is ready for chpid: 0xF0 device: 0x404
AWSDSA010I AWSOSA is ready for chpid: 0xF0 device: 0x405
AWSDSA010I AWSOSA is ready for chpid: 0xA0 device: 0x400
AWSDSA010I AWSOSA is ready for chpid: 0xF0 device: 0x406
AWSSTA059I System initialization complete
AWSSTA082E Device manager 28883 (AWS3274), device 0701 has terminated
AWSSTA012I All configured subsystems started
Rational Unit Test started
CPU 0, zPDTA available and working. Serial - 79 2/14/2013 CPU 1, zPDTA available and working. Serial - 79 2/14/2013 End of zPDTA Status display
nohup x3270 -model 4 localhost:3270 &
nohup: redirecting stderr to stdout
ipl a80 parm 0a82zw for warmstart
Mon Dec 24 01:56:38 ibmsys1@amozpdt01:/z1>
Display PSW:
on Dec 24 02:23:46 ibmsys1@amozpdt01:/z1>d psw
PSW for CPU 0 00002000 80000000 00000000 000019D2 --> B22C 0006

Display token:
Mon Dec 24 02:25:58 ibmsys1@amozpdt01:/z1>token
CPU 0, zPDTA available and working. Serial - 79 2/14/2013
CPU 1, zPDTA available and working. Serial - 79 2/14/2013
End of zPDTA Status display

Display architecture mode:
Mon Dec 24 02:26:04 ibmsys1@amozpdt01:/z1>d r
CPU 0 in Z architecture mode

Query CPU 0:

Mon Dec 24 02:32:04 ibmsys1@amozpdt01:/z1>query 0
Status for CPU 0 (GP ,Primary ,Operational ) : Running

Query CPU 1:
Mon Dec 24 02:32:29 ibmsys1@amozpdt01:/z1>query 1
Status for CPU 1 (GP ,Primary ,Operational ) : Stopped
Mon Dec 24 02:32:34 ibmsys1@amozpdt01:/z1>

Why CPU 1 is not available. I tried to restart it. But its going to disabled state.

Have anyone faced the same issue? our system going down frequently because of this.
Is there any problem in the base system?

Try to change your device map in order to instruct the system to only use one processor.

Thank you for your reply.
currently system using only one. i wanted to make both available.

another system going down frequently in Linux box, i see the below message.

hu Dec 13 01:15:22 ibmsys1@amozpdt01:/z1>AWSSTA081E Process ID 13949, component APSMON, has terminated
AWSSTA084I ... performing restart of process APSMON
AWSSTA081E Process ID 13950, component CPU, has terminated
AWSSTA086E ... system wide log out in progress
AWSSTA125I System shutdown in progress ...
AWSSTA141E System failure
Could you please let me know, what could be the reason?

Would you please use the command senderrdata, select option 5 for configuration file and either send to z1090@us.ibm.com or ftp the file per the senderrdata script.

Would you also please collect the contents of the z1090/logs directory from the userid used to run the z1090 instance. You can try the senderrdata option 8 and use the senderrdata script to ftp the file. I would suspect the compressed file of the contents from the z1090/logs directory would be too large to send as an attachment via e-mail. If senderrdata option 8 fails, please manually tar the contents of the z1090/logs directory and ftp to testcase.boulder.ibm.com, userid anonymous. Please put the file in the /toibm/hw directory. Please let me know the name of the file that is sent to testcase.

z1090 Functional Support

I had sent the senderrdata option 5 files created to the email provided

I’ll upload the /z1090/logs tar file and let you know.

You mentioned that the system has one CPU and two CPUs are defined in the devmap. Are you using hyperthreading with this system? Normally, the 1090 instance would not start if only only one physical CPU is available and you have defined two in the devmap. Would you please use the senderrdata command, option 5 to collect a configuration file of your system. This command must be started from the userid used to start the 1090 instance. You have an option to send this configuration file via ftp or you can send this file to z1090@us.ibm.com. If you choose to send via ftp, please let me know the name of the file.

In addition, we noticed that you are using version 8.0.1. We would recommend that you update your RDzUT version to a newer version. The most recent version is 8.0.3.2. This version is available via the service hub for RDzUT.

z1090 functional support