SQLStatement objects as attributes  Parsing NCM messages

Release Bulletin New Era of Networks Process Server Version 3.6.1 for Solaris, Windows NT/2000, AIX, HP

Date parsing

Problem: Incoming messages with a two-digit year representation do not convert to the proper century. An incoming date of 021804 would be translated as 1904-02-18.

Workaround: Either use 4-digit representations for the year or include the following information in your edl.

actions:

Example 1

integer myyear = two_digit_year.year()

if (myyear <= 1950)

{ myyear = myyear + 100 }

two_digit_year = myyear.toString() + "-" + two_digit_year.toStringFormatted("%m-%d")

Change the pivot year (myyear <= 1950) to a year that will be considered the pivot point between the 20th and 21st century. The logic behind it is that any two digit year below or equal to 1950 (00-50) will be recognized as in the 21st century (2000-2050). Any above (51-99) are in the 20th (1951-1999).





Copyright © 2002. Sybase Inc. All rights reserved. Parsing NCM messages

View this release bulletin as PDF