We finally gave up after hours and hours of trying to get it to work! I think its the fact that it needs tons of memory just to keep the Java engine happy and we cannot fix that at this time. I Hve asked IBM to comment but to date they say no one else is moaning about it so they cannot understand why I am having such problems. Maybe if enough people actually try to use it and let IBM know just how bad it is then they will make it better? I ended up just finding out how to work round it by calling the required functions directly as I have mentioned.

If you do get further than us let me know..

Chris..

It’s was a issue with the DNS entry and every request waiting for it to time out… if you could please post this document in case anyone else has the same issue that would be great:
http://www-01.ibm.com/support/docview.wss?uid=nas1b9e677063f24f859862575ee006b1881

I found one of your threads here…
“http://forums.systeminetwork.com/isnetforums/showthread.php?t=54991&page=2″

I think I’ve seen someone else report this issue on a forum too… people give performance tips however they aren’t aware of how “slow” things really are… it goes beyond some minor performance tweak.

Anyways if you found the answer please share! I’ve got a a few Linux clients and this is driving me nuts… We have iSeries web access going too, and it works but is pretty sluggish too.

I just ran a test and it definitely starts journalling on a restore? Without any more information I do not know what to say?

Chris…

Our process automatically starts journalling as the restore occurs? It does not matter what process you use, everytime an object is restored it should attach to the journal as long as it is there?

Does your restore process do that or do you have to relink to the journal manually afterwards?

When you are passing in the DSParms parameters you can use “Count” to determine how many structures there are and this can reference a PHP variable such as $num which is set within your script. When you use “CountRef” you must pass in the string of the parameter which is part of the description you are passing in to the program prepare. Basically you are saying look at one of the other variables that is contained in the parameter array I am using to prepare the program call. The following code sent by EasyCom cleared it up for me..

When you write :
array(“DSName” => “jrninfo”, “CountRef” => ‘numjrn’, “DSParm” => array(

‘numjrn’ represents a name inside the description, not a php variable.

So you also can write:
array(“name” => “numents”, “io” => I5_IN, “type” => I5_TYPE_INT),
array(“name” => “numjrn”, “io” => I5_IN, “type” => I5_TYPE_INT),
array(“name” => “dtaq”, “io” => I5_IN, “type” => I5_TYPE_CHAR, “length” => “10″),
array(“DSName” => “jrninfo”, “CountRef” => ‘numjrn’, “DSParm” => array(
(and put 1 to the numjrn parameter in the call).

I think this makes it all a lot clearer??

Chris…