Submitted by Anonymous (not verified) on Mon, 03/17/2014 - 00:00
Forums
IceBreak

Hi,

Can you help me with this error (see screen shot 1)? Can you see what is wrong?

Niels Liisberg

Mon, 03/17/2014 - 00:00

Permalink

Hi,

It is another version of IceBreak that causes the troubles. Typically it is InterForm on the library list – which also contains a (older) version SVC200 – the service program core in IceBreak.

If it is not signature violation in SVC200 then it can be signature violation in one of your own programs.

Do you know about binder sources? Does QSRVSRC sound familiar?

Best regards,
Niels Liisberg 

Hi Niels.

But I have not changed anything on DKSRV07.

Can you see why it gives this error?

I have restarted IceBreak and also deleted the existing 2 objects. Should I delete QASPSRC or something like that?

Hi,

Please see screen shot 2. This is a problem between two of your programs. So next time - Please examine your own code first.

Now: This is easy to fix – You need to compile all programs that use your service programs if you modify the service program or any of its components, in the way you have constructed your application now.

In a “real-world” service-program you need to build a QSRVSRC with all the exports and an unique “signature” of your service program. In this case you don’t have to recompile your client code (the code that uses the service program).

Please read this article:
http://www.mcpressonline.com/programming/rpg/using-binding-language-wit…

Best regards,
Niels Liisberg 

Hi Niels,

Thanks for the help. I reconstructed all binding directory and recompiled all the programs. Now it is OK.
I’ll check out the link you sent me to better understand the service program features.

By the way, where did you find the log screen viewed in screen shot 2?

Hi,

When you run an IceBreak program from the browser, it will spawn an IBMi job.

And as long as your server is in development mode and your system hive is enabled (which it is by default) then you can find the job name as easy as running the DSPJOBLOG command in the system hive in your browser. That is:

/system/dspjoblog

For my server that will be http://dkexp05:60000/system/dspjoblog (see screen shot 3).

In most cases all you need is in this list since it is the formatted version of the job log. However if you need more informations like spool files, job invocation and details about the job log then follow this procedure:

You now have the associated job name for your job in the first line of the job log. In my case you can see the first line contains 322183/NL/SYSTES0001 (see screen shot 3).

So if you take a 5250 session and enter the IBMI command where you paste the job name in just after the DSPJOB – like:

===> DSPJOB 322183/NL/SYSTES0001

Then you will have all normal job informations for your IceBreak job.

On the other hand – When your server is in production mode or you run it in *SHAREDPOOL or you have disabled the system hive then you have no chance to get these informations.

Best regards,
Niels Liisberg