DSXchange

APT_STRING_PADCHAR is for parallel jobs only. Use Convert() to remove any Char(0) values, and Fmt() to generate space padding. For example, if the output field is 15 characters wide

The project name is in the header of the VOC file. You use the VERIFY.SQL command to repair it. First use VERIFY.SQL without the FIX option to verify what will be fixed. VERIFY.SQL SCHEMA projectname Then use VERIFY.SQL with the FIX option - you will need to be the Administrator for this. VERIFY.SQL...

There's no space between the date and time portions of your timestamp. But the format string specifies that there should be.

Create a node pool containing just server2 and constrain your stages to execute it in.

Or set up your default node pool to contain just server2 and use the environment variable APT_PM_CONDUCTOR_NODENAME to specify server1 as the conductor node.

There is no capacity to use regular expressions in a trim function. You could create a stage variable containing all the non-numeric characters, and use Convert() to remove these from the input column.

Welcome aboard.

There is no upper limit on the string that you can store in the user status area.

Actually that's not true. But there's no practical limit. The actual limit is somewhere near the larger of the amount of free memory that is available and approximately 2GB.

There is no UNIX command. Job logs are database tables.

Purging a job log involves not only deleting records from the table but also updating a number of control records.

Set auto-purge defaults for the project using the Administrator client, you can override these defaults for particular jobs.

Post your record schema.

This is pattern action language. & is the pattern, the COPY commands are the actions. & means "a single token of any type". See Pattern Action Reference Guide page 1-4 for version 7.5. This part of the COUNTRY rule set is the part that assigns the default country code and sets the indicator ...

This has been answered a bajillion times. Search for the answer.

The problem is between the keyboard and the chair. You have declared a record length of 426, and a set of column widths that total 425.

The "solution" is to get it right.

This error comes whenever any filesystem, which is mentioned is the configuration file, is full or tending to full. If you cat the config file you can see some resource disk filesystem and resource scratchdisk filesystem. To resolve this issue delete the old files(unnecessary files) from the files ...

So you need the equivalent of the timestamp of this time on the previous day to a particular timestamp? Download the routines from this site and you will find one (AddDaysToTimestamp) that does timestamp arithmetic. Use -1 as the Days argument.

You will never prevent the logs from being created. Jobs won't run unless the log (a database table in the local Repository) can be opened for writing. And some entries just can't be suppressed. Let me ask again why you wish to do this.

This is where you need to involve your official support provider. There is (currently) less expertise here with version 8 than with previous versions; that is, we have not yet had the opportunity to have a solid "play" with it yet.