DSXchange

There are different EBCDIC code pages. Your mainframe folks have clued you in by telling you they are using CCSID 037. The ! character is an example that would translate differently if using, e.g., CCSID 500. You need to experiment with the EBCDIC NLS code pages and use whatever matches up to CCSID ...

From your last description, I would guess that it is related to the load on your server during those morning runs. One possible cause of a long Startup time is an overloaded server. Also keep in mind that "Startup time" is a misleading label. Think of it as more of a bucket of time that wa...

I'm still mostly old school when it comes to analyzing resource usage. I like watching an interactive nmon window along with having a Director monitor window open.

It sounds like your admins have already captured the relevant data for you.

Mike

I guess we were typing at the same time... Your data volumes seem insignificant. The fork lookup is a potential problem with buffering and deadlocks. All of the reference data for a normal lookup needs to be preloaded to memory. Replace the lookup stage with a join stage for the more typical fork jo...

You didn't answer any of my questions... With your design using the lookup stage, I would check if you have enough physical memory to support the reference data being preloaded to memory (assuming you are doing a normal lookup). If you exhaust physical memory, using swap space will generate a lot of...

What is the size of the file being read? What is the size of the file being written? What other stages are in your job design? What other processes are running on the server at the same time? Are you doing anything in a Before-job subroutine?

Mike

You seem to have a weak interface contract with your data provider.

If you want to be nice and handle all possible variations, you'll have to do a lot of extra work.

So what will you do with "16122"? January 22 or December 2?

Mike

The transformer stage is frequently the way to avoid implicit type conversion warnings, transforming larger strings into smaller strings, and other such things as might require an explicit transformation. You could try replacing the transformer with a copy or a modify to see if the warnings you want...

Enter the dsjob command without any options and review the syntax requirements. There are multiple options for authentication. In your working example, you have authenticated directly with the engine tier. In your timeout example, it does not appear that you have provided any of the acceptable authe...

By "continuous mirroring mode", I'm going to assume you're saying this is an ISD job. If so, you'll need to find the documentation on the data source restrictions for designing ISD jobs. I think this was in an IBM Redbook that's been out there for years.

Mike

This seems likely to come down to a permissions issue. You will need to work with your Information Server and DataStage Admins since resolving it will very likely depend on how user and group security is set up and administered for your installation. Some thought starters: Using internal registry or...

The DB2 Connector can do partitioned reads even when the underlying source table is not partitioned. I always prefer the DB2 Connector over the ODBC Connector, so I don't know about the ODBC Connector's parallel read capabilities. The fact that you're seeing all rows broadcasted to every processing ...

Yes. The transformer inside the shared container. For whatever reason, RCP seems to fail, which causes those "Could not find input field" errors that you are experiencing. And it's not all transformers inside a shared container since I have others where RCP worked fine... I never could pin...

I think this is a likely bug. I've run into a similar issue on version 11.3. I ended up implementing a workaround for expediency. My unverified thinking was that it was somehow related to having a transformer stage as first stage after the input with RCP enabled. I ran into this bug on two different...

Enable DSODB. Configure it to capture the level of detail that you desire. The information you need will be sitting in a database table for you. You can also use some of the reporting environment variables such as $APT_PM_PLAYER_TIMING to capture that detail into the job log...there is another repor...