Variable "APT_AUTO_TRANSPORT_BLOCK_SIZE" missing

just4geeks · Post by **just4geeks** » Tue Mar 13, 2007 10:41 am

I am having another problem with running jobs at CLI.

When I run a job as following, it works fine.

dsjob -run -wait projectname jobname

Then I ran it as following ,

Code: Select all

dsjob -run -wait -jobstatus projectname jobname

it aborted with the following error.

Code: Select all

From previous run 
DataStage Job 91 Phantom 10527
The variable "APT_AUTO_TRANSPORT_BLOCK_SIZE" is not in the environment.

Why does it do that? Thanks for your time.

DSguru2B · Post by **DSguru2B** » Tue Mar 13, 2007 10:52 am

What happens when you remove the -wait and just put -jobstatus?

just4geeks · Post by **just4geeks** » Tue Mar 13, 2007 2:52 pm

DSguru2B wrote:What happens when you remove the -wait and just put -jobstatus?

Yeah, it worked.

loveojha2 · Post by **loveojha2** » Wed Mar 14, 2007 2:28 am

Yeah, it worked.

Does anyone know why it did not work with -wait and what is this APT_AUTO_TRANSPORT_BLOCK_SIZE?

kumar_s · Post by **kumar_s** » Wed Mar 14, 2007 2:37 am

The option jobstatus it self will wait till the job gets finished, to fetch the status of that run.

loveojha2 · Post by **loveojha2** » Wed Mar 14, 2007 3:32 am

Got this from the manual:

Setting Transport Block Size
You can set the APT_AUTO_TRANSPORT_BLOCK_SIZE to True to have DataStage automatically calculate the block size for transferring data for transferring data internally as jobs run.

The APT_DEFAULT_TRANSPORT_BLOCK_SIZE variable defines the block size used otherwise. By default it is set to 32768.

But its under Parallel Job Environment variables, not sure if its applicable in server jobs also and how it is appearing in the error text pasted.

kumar_s · Post by **kumar_s** » Wed Mar 14, 2007 5:41 am

Now I doubt, if its somehow PX job and wrongly parked here.

just4geeks · Post by **just4geeks** » Wed Mar 14, 2007 6:34 am

kumar_s wrote:Now I doubt, if its somehow PX job and wrongly parked here.

I confirm that it is a Server Job.

ray.wurlod · Post by **ray.wurlod** » Wed Mar 14, 2007 7:02 am

How was it resolved?

DSguru2B · Post by **DSguru2B** » Wed Mar 14, 2007 8:08 am

just4geeks wrote:
DSguru2B wrote:What happens when you remove the -wait and just put -jobstatus?
Yeah, it worked.

Is that what your looking for Ray ji ?

ray.wurlod · Post by **ray.wurlod** » Wed Mar 14, 2007 6:17 pm

No. I need to know WHY, with both options in place, this error gets generated. And therefore why removing one - either, perhaps? - fixes the problem. In short, how it was resolved. Not what was done.

DSguru2B · Post by **DSguru2B** » Wed Mar 14, 2007 6:20 pm

O okie. Cool.

chulett · Post by **chulett** » Wed Mar 14, 2007 6:40 pm

I for one don't see the connection between the two options and the APT variable issue. I know, back in my younger and foolisher days, I've used both without knowing better and it didn't throw that error. Maybe it helps I don't have PX, only a Server license.

Put both back, see if the error repeats. Or someone else use both and see.

DSguru2B · Post by **DSguru2B** » Wed Mar 14, 2007 6:43 pm

I have tried it as well. No issues at my end.

ray.wurlod · Post by **ray.wurlod** » Wed Mar 14, 2007 6:57 pm

Maybe some kind soul just added APT_AUTO_TRANSPORT_BLOCK_SIZE in to the OP's project via the Administrator client.