IBM Sterling Transformation Extender

Sterling Transformation Extender

Come for answers, stay for best practices. All we're missing is you.


#Sterling
#Supplychain
 View Only
  • 1.  SHL Adapter Argument Limitations

    Posted 04/19/06 04:31 PM

    Originally posted by: SystemAdmin


    Does anybody know of a adapter command length limitation associated with the SHL adapter running on an AIX server?

    I'm receiving a "-99999" return code (RC) when using the SHL adapter within a GET function in an output card rule. This RC usually means there's something wrong with the format of my adapter command string. And because the adapter isn't getting executed, I'm not getting any trace output to help in debugging the problem. Here's a scaled down version of the GET portion of the rule...

    GET("SHL","-CLI %cmd_line_int% -CMD " + TEXT(D1 Data:PConfig) + " -TRACEV %op_traces%purge.mtr","")

    ... which at runtime resolves to...

    GET("SHL","-CLI /usr/bin/ksh -CMD /mercator/mercappl/op/maps/es_purge_mail_arch.ksh /mercator/mercator/appl/mail/archive/ 90 /ediarch60/ /mercator/merchist/op/logs/ /mercator/mercappl/op/temp/ -TRACEV /mercator/mercappl/op/traces/purge.mtr","")

    What the shell script is doing isn't important, but I do want to pass it all 5 arguments and cannot without the adapter failing. Strangely enough, I am able to get this adapter command to work when I send this adapter command without the fifth (last) argument. So it would seem that an adapter string of "/mercator/mercappl/op/maps/es_purge_mail_arch.ksh /mercator/mercator/appl/mail/archive/ 90 /ediarch60/ /mercator/merchist/op/logs/ /mercator/mercappl/op/temp/" (158 characters) is not acceptable, but an adapter string of "/mercator/mercappl/op/maps/es_purge_mail_arch.ksh /mercator/mercator/appl/mail/archive/ 90 /ediarch60/ /mercator/merchist/op/logs/" (130 characters) is OK.
    #DataExchange
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender


  • 2.  Re: SHL Adapter Argument Limitations

    Posted 04/20/06 05:14 AM

    Originally posted by: SystemAdmin


    What version? Total command line should work if under 260 chars in earlier versions. In 8.x this has been expanded.

    You might want to try a RUN command and pass the data as a target.
    #DataExchange
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender


  • 3.  Re: SHL Adapter Argument Limitations

    Posted 04/20/06 06:31 AM

    Originally posted by: SystemAdmin


    It would seem to me that you have one too many arguments for the GET function.

    code:1:4a403916d5
    GET("SHL","-CLI /usr/bin/ksh -CMD /mercator/mercappl/op/maps/es_purge_mail_arch.ksh /mercator/mercator/appl/mail/archive/ 90 /ediarch60/ /mercator/merchist/op/logs/ /mercator/mercappl/op/temp/ -TRACEV /mercator/mercappl/op/traces/purge.mtr","")
    [/code:1:4a403916d5]

    Try using this with single quotes around your command string:

    code:1:4a403916d5
    GET(
    "SHL"
    ,"-CLI /usr/bin/ksh "
    // Initiating single quote for CMD
    + "-CMD '/mercator/mercappl/op/maps/es_purge_mail_arch.ksh "
    + "/mercator/mercator/appl/mail/archive/ "
    + "90 "
    + "/ediarch60/ "
    + "/mercator/merchist/op/logs/ "
    + "/mercator/mercappl/op/temp/' " // Trailing single quote
    + "-TRACEV /mercator/mercappl/op/traces/purge.mtr"
    )
    [/code:1:4a403916d5]

    Hope this helps,
    John
    #DataExchange
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender


  • 4.  Re: SHL Adapter Argument Limitations

    Posted 04/24/06 06:49 PM

    Originally posted by: SystemAdmin


    Thanks for the great suggestion John. In fact, I had included single quotes in my command string through the use of SYMBOL(39). The reason I may have forgotton to include this in my initial posting is because my command string (everything after the "-CMD" but before the "-TRACEV") is actually built in predecessor map rules. But the final composite command string is wrapped in single quotes, like this:

    /* Full command line to be run */
    ="" + SYMBOL(39) + D05 DataVAL Data:PurgeConfig + " "+ D06 DataVAL Data:PurgeConfig + SYMBOL(39) + ""

    Based on Jeff Smoley's previous reply, I'm more inclined to believe I've hit some kind of limitation on the command string length. We're running this under release DSTX 7.5.1 and the entire GET command, starting with and including the "GET", and including everything within the GET's parenthesis, is 261 bytes. Assuming that this is what Jeff was referring to, then I've got to wait until we upgrade to 8.X before I can implement this the way I want.
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender
    #DataExchange


  • 5.  Re: SHL Adapter Argument Limitations

    Posted 04/25/06 01:56 AM

    Originally posted by: SystemAdmin


    You could save a few characters by using -TV rather than TRACEV.
    Can you do anything to trim the path lengths?
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender
    #DataExchange


  • 6.  Re: SHL Adapter Argument Limitations

    Posted 04/25/06 05:32 AM

    Originally posted by: SystemAdmin


    Change the name of the script to epms.ksh would save a lot too.
    temp to tmp traces to trc. UNIX people are supposed to not type more than 4 characters at a time :-)
    #DataExchange
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender


  • 7.  Re: SHL Adapter Argument Limitations

    Posted 04/25/06 11:01 AM

    Originally posted by: SystemAdmin


    This might be a bit of a stretch, but give it a try.

    Change the case of your "-CLI" to lower case. On page nine of the i:0e8396545aBatch File and Shell Script Adapters Reference Guide[/i:0e8396545a] PDF, the shell script documentation shows it lower case as opposed to the Batch side.

    Worth a shot. I keep mine all lower case on the SHL adapter regardless of environment and so far they always seem to work.

    John
    #IBM-Websphere-Transformation-Extender
    #DataExchange
    #IBMSterlingTransformationExtender


  • 8.  Re: SHL Adapter Argument Limitations

    Posted 05/02/06 11:51 AM

    Originally posted by: SystemAdmin


    Jan/Jeff/John: Thanks for the good suggestions. I was able to get it to work by trimming things down a bit. I guess the next thing to do would be to upgrade to 8.0, where this isn't as big of a problem (but apparently still a problem, nonetheless). Again - I appreciate the help.
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender
    #DataExchange