*SSHD Job generating joblogs every second

I have an open ticket with IBM but at this stage they are suggesting a
test PTF for the issue which is going to take days.

The other morning I had a call from a site we look after where users could
not sign on.

Below is the initial steps taken and details of two joblogs showing
errors. Stopping *SSHD stops the issue.

The system generated over 160000 jobs which had joblogs *pending and
exceeded the maximum jobs.

Anybody seen anything like this or have any comments/suggestions ?


System would not allow any new jobs as system tables were full.

Have increased MAXJOBS to allow new jobs to be started.

DSPJOBTBL F11 shows large numbers of joblog pending

WRKJOBLOG shows very large number of job(QP0ZSPWP) being created for user
QECOFR approximately every 1 second.

Many of these are relating to CPFA09C Not authorized to object. Object is
/QSYS.LIB/EN_US.LOCALE.

Also following messages;
sshd[1540655]: rexec line 96: Deprecated option UsePrivilegeSeparation
sshd[1540655]: Invalid user dick from 190.111.249.133 port 56678
Space offset X'00000000' or X'0000000049424D55' is outside current limit
for object QPADEV0002CCLFC 101610.
PASE for i ended for signal 11, error code 1.
Value for call stack counter parameter not valid.
Application error. CPFB9C6 unmonitored by QP0ZPCPN at statement
0000000278, instruction X'0000'.
This job ended abnormally.
Job 077740/QSECOFR/QP0ZSPWP ended on 15/01/20 at 00:00:10; .029 seconds
used; end code 30 .
This has only started from 00:00:00 on 15/01/2020 Eg Today

Job . . : QP0ZSPWP User . . : QSECOFR Number . . . : 109232

Not authorized to object. Object is /QSYS.LIB/EN_US.LOCALE.
Job ended abnormally.
Job 109232/QSECOFR/QP0ZSPWP ended on 15/01/20 at 13:14:27; .025 seconds

used; end code 30 .



Don Brown





______________________________________________________________________
This email has been scanned for computer viruses. Although MSD has taken reasonable precautions to ensure no viruses are present in this email, MSD cannot accept responsibility for any loss or damage arising from the use of this email or attachments.
______________________________________________________________________