Re: SBMJOB #LIBRARY problem.

Oh, but than again. I think you have to remove the S36Environment on the
machine where it resides, or remove #LIBRARY on the ADDLIBLE command. Either
will help.

Pjotr

Pjotr wrote:
On the machine where #LIBRARY is loaded the S/36 Emulation is
installed. On the other one it does not.
You can install it on the machine that does not have a #LIBRARY. Do a
GO LICPGM and choose 11. Than add:

5722SS1 *COMPATIBLE OS/400 - System/36 Environment
while having mounted the install CD first.

HTH
Pjotr

gb wrote:
Is #LIBRARY in the QUSRLIBL system value (on the erring machine)?

GB

<rmcc70@xxxxxxxxxxx> wrote in message
news:1120460288.253172.72140@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi All and TIA,

I am trying to submit a job and getting the following error SSP0139
(joblog below). The machine is at v5r1 and has a twin at v5r2 which,
identically setup, doesn't get the error. Basically the job errors
because it is trying to add #LIBRARY to the library list (user
section) when it is already there. I have checked many things eg
DSPS36, Routing entries, Jobd's etc but can find nothing obvious.
Basically one machine will let you run the job and the other errors
on the submit command.

Can anyone help?

Regards

rmcc70

SGID TYPE SEV DATE TIME FROM PGM
LIBRARY INST TO PGM LIBRARY

CPF1124 Information 00 04/07/05 03:31:05 QWTPIIPP
QSYS 067E *EXT
Message . . . . : Job 151241/RMCC70/QPADEV000N started on 04/07/05
at 3:31:05 in subsystem QINTER in QSYS. Job entered system on
04/07/05 at 03:31:05.
CPF2103 Escape 40 04/07/05 03:31:05 QLICUSRL
QSYS 018B QEXSIGN QSSP
Message . . . . : Library #LIBRARY already exists in library list.
Cause . . . . . : The library #LIBRARY already exists in the
library search
list. The library was not added. Recovery . . . : If #LIBRARY is
the library you specified omit the command. If you did not specify
library #LIBRARY then change the library name (LIB parameter). Then
try the command
again.
SSP0139 Escape 99 04/07/05 03:31:05 QEXSIGN
QSSP 0CF9 *EXT
Message . . . . : Unable to add library #LIBRARY to user portion
of library
list.
Cause . . . . . : Library #LIBRARY could not be added to library
list.
Recovery . . . : Look at the job log for messages that indicate
reasons
for this error. Use the Display Job Log (DSPJOBLOG) command to look
at the
job log. Correct the error condition and then try the job again.
PF2494 Diagnostic 99 04/07/05 03:31:05 QMHUNMSG
QSYS 04D6 *EXT
Message . . . . : Exception message was sent to a location
preceding the
first entry in the call stack.
Cause . . . . . : If the message was sent, the combination of call
stack
entry name and call stack counter produced a location that precedes
the first entry in the call stack. This condition can also result
if the message was resignaled from the first entry in the call
stack.


.

Relevant Pages

  • Re: The Promise of Forth
    ... After awhile I ... found a chart of the Z80 command set and I wrote a disassembler, ... stack operator. ... Then I got my own PC and I tried out Pygmy Forth. ...
    (comp.lang.forth)
  • Re: Analysing a minidump cause by a release build
    ... Since you got a .dmp file generated from the .dump /ma command, you have a complete picture of the process at the time of the dump creation. ... You indicate that you see only one call stack. ... I can also see that the WER process wrote a minidump to my Local Settings\Temp folder, but access to it is denied. ...
    (microsoft.public.vc.debugger)
  • TIP #211: Add Full Stack Trace Capability
    ... ADD FULL STACK TRACE CAPABILITY ... This TIP proposes adding a new subcommand to the *info* command, ... flag to the *level* subcommand, to get a list of all the current stack ... % proc bob { ...
    (comp.lang.tcl)
  • Re: SBMJOB #LIBRARY problem.
    ... Check the initial library lists on each machine for the user profiles in question. ... will let you run the job and the other errors on the submit command. ... stack entry name and call stack counter produced a location that precedes the first entry in the call stack. ...
    (comp.sys.ibm.as400.misc)
  • Re: SBMJOB #LIBRARY problem.
    ... You can install it on the machine that does not have a #LIBRARY. ... the library you specified omit the command. ... first entry in the call stack. ... the first entry in the call stack. ...
    (comp.sys.ibm.as400.misc)