DSXchange

Search DSXchange for APT_STRING_PADCHAR

Cool.

A Sequence job is a special case of a Server job.

That's one reason server jobs are going to remain in the product indefinitely.

This linkage is not maintained in DS_ROUTINES. Assuming that you are accurately maintaining the Dependencies tab, you can use Usage Analysis in Manager to determine which jobs use the selected routine. Dependencies are job properties and are stored in DS_JOBOBJECTS. But you have to have maintained t...

Take a look at the Score.

In particular, are there inserted tsort operators on the inputs to the Join stage? Inserted buffer operators? Either of these will "block" the pipeline.

My test results are as follows. aString: "Austin+Texas;Blue+Sky;air-baloon+ride;Laptop+Pad;Grass+Green;Deep+;" aSearchString: "Blue" Ans: "Sky" Here is the routine: FUNCTION ReturnSecondOfPair(aString, aSearchString) * Convert string into dynamic array. String = Convert...

You can not perform blocking operations in parallel jobs.

In this case you can not write to a Data Set and read from the same Data Set in the same job.

There is no Primary Key index on hashed files (unless you create one, and it will never be used). The hashing algorithm method of locating a record is far more efficient than using an index, since the algorithm requires no I/O whatsoever.

This record stores the parameter values entered when the job was scheduled. If the system can not find them, it suggests that the record may have been deleted, perhaps by the job being recompiled subsequently.

The best way to tune the Sort stage memory property is to measure its memory consumption using Performance Analysis (maybe even Resource Estimator) tool. Increase memory until the tsort operator stops using disk. Beware that if APT_TSORT_STRESS_BLOCKSIZE is set it overrides any memory property setti...

The obvious question: did you re-compile the job after making the changes?

Examine the score. Satisfy yourself that there is no Modify stage (operator). Try using the stage on the other end of the link as the stage name argument to DSGetLinkInfo().

The IBM website contains up to date information about operating system compatibility.

This error code can also occur if the connected client has been idle for more than the timeout limit set (via the Administrator client) from that machine. The agent process (dsapi_server) on the server monitors inactivity and will terminate the connection. The user returning to the client after this...

There's more. Hashed files automatically re-use space freed by deleting records.

Is "WITH NONE" valid ODBC syntax? (Note that I am not asking about the back end database here, I am asking about ODBC grammar.)