Originally posted by: phiiiiiiiil

Hello,


I've a map that return this warning message :


Map completed (34): Too few pages requested, more allocated (6160.803 seconds)


This map run successfuly every day but once a year it should treat a large amount of data. So I tried to run the dtxpage tool in order to increase performance and thus avoid this warning message but it return :


Map "my_map" has return code 9. dtxpage exiting.


Does anyone have an idea what it could mean ?


Thanks in advance.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: Kepa_Screen

The map can complete but can be optimized by increasing pages count.

Just change map settings increasing page count from 8 to a higher number.
( map settings : workspace )

Message was edited by: Kepa
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: jvanboga

In the older versions a Return Code of '9' indicated target not available. Which indicated either a permissions, path or file name conflict. In this case, based on your other messages, increasing your page counts should help.

Haven't found a generic return code document for IBM's versions of TX.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: NancyR

In any of the Design Studio tools pull down the Help-->Contents. In the left-hand window, click Map Designer. Then open the last topic, Error and Warning Messages. All the map execution error and warning messages are there.

Alternatively, look in the Map Designer Reference Guide Chapter 22.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: jvanboga

That's fine if you are licensed to use Design Studio or have access to the studio when dealing with an oncall issue. Doesn't help much otherwise.

In this shop there are a number of non-development and oncall support people that review failed map log files. Dependng on the issue they either deal with or escallate it. More often than not a production failure is not due to a coding issue. Usually, those issues are environmental or data related. Regardless, my ability to give them access to the 'Map Return Code' pdf has gven me the ability to remove myself a bit from most day-to-day production issues and empower other people at the same time.

PS: I must have an old copy of 8.0 and 8.1 doc but from what I can see "Map Designer Reference Guide" does not contain a complete list of map return code does it? I believe that the complete list of return codes are spread thru several documents. Also, because the last version of TX isnatlled in our test environment requires Eclipse you need to be logged into a machine that has the documentation installed to effectively access them. Again, it makes it difficult for BA's and others to help debug problems.

Message was edited by: jvanboga
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: NancyR

I only have the current versions of the Online Library for those two releases and both have a complete list in chapter 21 of the Map Designer Reference Guide.

If you're tired of being bothered to interpret non mapping rule related errors why not make a copy of the error messages and make them available to your on-call crew?
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: jvanboga

Found in other documents and not in 'Map Designer Reference Guide' are all of the adapter, type tree and system error messages. I suppose I could piece something together from each PDF and add as I identify other missing codes.

To be fair, though, many of the descriptions/explanations of return codes are a little better in the more recent documents.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: phiiiiiiiil

Indeed, it was due to a target not available. A look in the map designer shows that a parameter were not correctly configured. The map is triggered by a script shell and the parameters are overwritten by this one. That why this old good map runs for years.


Now dtxpage can run the map and return :


Optimal page settings for "my_map" are SIZE: 0 COUNT: 0 ??!!


I think I'm going to follow the advice of Kepa :


"...Just change map settings increasing page count from 8 to a higher number. ( map settings : workspace )..."


Thanks for you all.


Have a nice day.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender