retrieve items from list and convert (ODBC)

Doug,

OK to start with the xlateOutVals in this example

{{{2011-04-01 10:00:26.000} {2004-01-20 08:39:06.000} 154 1864}}

is a nested list (I think you tried too hard to make xlateOutVals a list).

The first nest only has one element and it is:

  {{2011-04-01 10:00:26.000} {2004-01-20 08:39:06.000} 154 1864}

The above is what I think you really want but to continue…

The second nest is:

   {2011-04-01 10:00:26.000} {2004-01-20 08:39:06.000} 154 1864

within this nest is another set of lists (the 2 date/time elements) which have 2 elements each.

In order to get the date you want you first have to properly navigate the list you have set up. I would suggest trying to reduce the nesting (share your code and perhaps we can assist with getting that pared down).

Once you get to the date portion of the date/time element (index 0 of that list) you will get something like 2011-04-01.

Then use the clock command.

set junk [clock format [clock scan “2011-4-01”] -format %Y%m%d]

The litreral with the date above will be replaced with the appropriate lindex once we get your list cleaned up.

Doug,

I have created multiple outbound from one inbound in the past by using xmpstore.

With that technique, I needed to use a CALL Action in the Xlate to invoke the proc rather than a COPY Action.

Doug,

You only need to use the date portion for what you want.

The date/time is a list in and of itself so you can lindex into that list as well.

For example

set clock1  [lindex [lindex [lindex $xlateOutVals 0] 0] 1]

    at this point you have {2004-01-20 08:39:06.000}. This is a list. Now you only really need the first element of the list (2004-01-20). So if you do this:

set junk [lindex $clock1 0]  <– this should give you just the 2004-01-20

Or you could just increase your indexing above to get the same thing.

Now do your clockformat/clockscan with the junk or clock1 variable (whichever indexing method you used).

The command does not handle the .000 at the end of the time.