DSXchange

Start Loop activity properties should be able to accept job parameter references enclosed in sharp signs.

Do both cron.allow and at.allow contain an entry for dsadm (or whatever your Engine credentials specify)? Note, too, that one-off executions may be handled by at rather than by cron.

Still no.

When you run the job don't choose Run Now on the Scheduler tab. Choose either of the other two options. As to the second part of your question you will need to be more specific about what you mean by "send" - but typically you can grab results using the command line interface or the REST A...

What have you tried? Did it produce the results you expected? If not, what results did it produce?

This really only needs to be an output link constraint expression in a Transformer stage. There is no need for If..Then..Else.

This suggests either that APT_CONFIG_FILE environment variable has not been set in the project or, perhaps, that its default value has been given as the special value $PROJDEF in the job's parameters. The latter case is just something you have to live with.

It can be very finicky about versions. Recently I had to uninstall .NET Framework 4.6.5 on the client tier and install version 4.0.

If an User is assigned with Operator role, the DirectoryCommand.sh outputs role as "DataStageOperator", but when an User is assigned to an Operator group, then DirectoryCommand.sh outputs role as "DataStageOperator(I)". Any guess about this (I)? I am just curious about this (I)....

And if you're allocating memory to local variables, simply free those in the usual fashion before returning.

Did you verify that DSOpenJob() worked correctly? The easiest way is to try to use the job handle for something innocuous, such as reporting the job name, then testing whether that returned an error code (typically DSJE_BADHANDLE).

Yes, that will work. Fewer resources might be used by (assuming there are no ":" characters in the user status value.

A1. See answer from rkashyap. You have to have configured the network alias, so that either machine can be known by the same name.

A2. Yes, but it's possibly a little bit more complex that that for WAS. The information provided in the link will explain in detail.

You need to re-install the Engine tier, this time choosing to install NLS.

Once LDAP authentication has been configured, all of the administrative facilities around users and groups in the web console for Information Server will use the LDAP-connected user registry. That is, you assign Information Server suite and product roles to AD users or groups. Similarly, when config...