APT_PHYSICIAL_DATASET_BLOCK_SIZE=?

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
muralidwhds
Participant
Posts: 39
Joined: Sat Jul 05, 2008 3:25 am
Location: chennai

APT_PHYSICIAL_DATASET_BLOCK_SIZE=?

Post by muralidwhds »

Hi,

How much value can i put the Administrator.

Here IBM has suggested "set these value to match the record length which should be greater than any value reported in the log"

So could you please tell me where can i get this value?
MALLI MURALI
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

This parameter does not affect server jobs.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
muralidwhds
Participant
Posts: 39
Joined: Sat Jul 05, 2008 3:25 am
Location: chennai

Abnormal termination of stage xxxxxx detected

Post by muralidwhds »

Here i am going to migrate datastage jobs from the Datastage V7 To V8 in Server Edition.

In one if job has throwing warning message 'Abnormal termination of stage xxxxxx detected' in DS V8 in Server Edition.

But the same job running successfully in DS V7.

This job has reading the data and updating the flag in same table in db2 database.


Please advise on this how can i fix this issue.
MALLI MURALI
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Reset the aborted job from the Director and let us know the contents of a "From previous run..." log entry if one shows up when you do so.
-craig

"You can never have too many knives" -- Logan Nine Fingers
muralidwhds
Participant
Posts: 39
Joined: Sat Jul 05, 2008 3:25 am
Location: chennai

Post by muralidwhds »

From previous run
DataStage Job 1 Phantom 12624
Job Aborted after 1 errors logged.
Program "DSD.WriteLog": Line 253, Abort.
Attempting to Cleanup after ABORT raised in job MCYRESETJOB.

DataStage Phantom Aborting with @ABORT.CODE = 1
MALLI MURALI
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

It would seem you are running the jobs with a "warning limit" of 1. How is it being executed?
-craig

"You can never have too many knives" -- Logan Nine Fingers
muralidwhds
Participant
Posts: 39
Joined: Sat Jul 05, 2008 3:25 am
Location: chennai

Post by muralidwhds »

we are running the ds jobs from unix shell script passig the 9 parameters as one of parameter as 1 (if one warning is generated the job has failed).


Here i am going to migrate all DS V7 jobs to DS V8 in Server Edition.

Please find the my job design:

Source Table A -------> Transformer ------> Target Table A

Source Table B --------> Transformer ------> Target Table B

Source Table C ---------> Transformet ------> Target Table C


in this job design passing parameters are DB2 Server Name, Databse name, User name, Password and one Environment varaible as $DB2CODEPAGE=1208

While running the above job in DS V8 the failure happend in only Table A job. here this job is reading the data from same table updating the same table with status code using transformer stge. Here the count of records coming and updating nearly 18,98970.

But Source Table B & Source Table C jobs are running sucessfully.


I tried with 2 records in Source Table A job which runs fine and updated with status code.

So please give me your thoughts on this how can i fix this issue in DS v8 Server Edition. But Same job running fine in DS V7 Server Edition.
MALLI MURALI
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

OK... so what was the warning that triggered the abort?
-craig

"You can never have too many knives" -- Logan Nine Fingers
muralidwhds
Participant
Posts: 39
Joined: Sat Jul 05, 2008 3:25 am
Location: chennai

Post by muralidwhds »

Warning message:

"Abnormal termination of stage MCYRESETJOB..TRF_TH detected"
MALLI MURALI
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

And when you reset the job after it aborted, was there a "from previous run" event logged? If so, what was in it?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

That was already posted. Odd, they seem to point at each other, seems like we are missing what actually caused the warning that brought the job down. :?
-craig

"You can never have too many knives" -- Logan Nine Fingers
muralidwhds
Participant
Posts: 39
Joined: Sat Jul 05, 2008 3:25 am
Location: chennai

Post by muralidwhds »

please find the below in detail log:

Abnormal termination of stage MCYRESETJOB..TRF_TH detected

Job Aborted after 1 errors logged.
Attempting to Cleanup after ABORT raised in job MCYRESETJOB.

From previous run
DataStage Job 1 Phantom 24758
Job Aborted after 1 errors logged.
Program "DSD.WriteLog": Line 253, Abort.
Attempting to Cleanup after ABORT raised in job MCYRESETJOB.

DataStage Phantom Aborting with @ABORT.CODE = 1

Resetting Job MCYRESETJOB.
Resetting stage MCYRESETJOB..TRF_PMT.
Finished Resetting stage MCYRESETJOB..TRF_PMT.
Resetting stage MCYRESETJOB..TRF_LEDGER.
Resetting stage MCYRESETJOB..TRF_TH.
Finished Resetting stage MCYRESETJOB..TRF_LEDGER.
Finished Resetting stage MCYRESETJOB..TRF_TH.
Job MCYRESETJOB has been reset.
MALLI MURALI
Post Reply