I get the following error when running a re-sync of the db.

-* This is system_settings_update_db_parms.fex
-* It is used in several places during the resynch process to insure that our DB parms are correct.
-* Code does not do edit checks on parms. We assume calling programs have dealt with this.
-INCLUDE PMF_GET_CURRENT_DATETIME
-* This is pmf_get_current_datetime.fex
-SET &CURRENT_DATETIME_INTERNAL = HGETC(8, 'HYYMDs') ;
-SET &SAVE_ECHO = ALL ;
-SET &ECHO = 'OFF' ;
-DEFAULTH &CHANGE_ID = ' '
-DEFAULTH &RDBMS = ' '
-DEFAULTH &PMF_DB_OWNER = ' '
-DEFAULTH &PMF_DB_TABLESPACE = ' '
-DEFAULTH &PMF_DB_INDEXSPACE = ' '
-SET &&ERR_MSG = '***Unkown error in system_settings_update_db_parms' ;
-GOTO :SYSTUDB_01A
-:SYSTUDB_01A
-**************************************************************
APP FILEDEF TEMPMFD DISK system_settings.mas
-RUN
-IF (0 EQ 0) AND ( 0 EQ 0) THEN GOTO :SYSTUDB_01B ;
-:SYSTUDB_01B
-******************************
-SET &TOPLINE = 'FILE=SYSTEM_SETTINGS, SUFFIX=' | DB2 | ',' ;
-WRITE TEMPMFD FILE=SYSTEM_SETTINGS, SUFFIX=DB2,
-WRITE TEMPMFD REMARKS='Temporary system_settings.mas', $
-WRITE TEMPMFD SEGNAME=SYSTEM_SETTINGS, SEGTYPE=S0, $
-WRITE TEMPMFD FIELD=VARIABLE_NAME, ALIAS=VARIABLE_NAME, USAGE=A64, ACTUAL=A64, $
-WRITE TEMPMFD FIELD=CHANGE_ID, ALIAS=CHANGE_ID, USAGE=A32, ACTUAL=A32, $
-WRITE TEMPMFD FIELD=UPDATE_DATE, ALIAS=UPDATE_DATE, USAGE=HYYMDs, ACTUAL=HYYMDs, $
-WRITE TEMPMFD FIELD=VARIABLE_VALUE, ALIAS=VARIABLE_VALUE, USAGE=A1024, ACTUAL=A1024, $
-GOTO :SYSTUDB_02
-:SYSTUDB_02
-**************************************************************
MODIFY FILE SYSTEM_SETTINGS
FREEFORM VARIABLE_NAME VARIABLE_VALUE
MATCH VARIABLE_NAME
ON MATCH COMPUTE
-INCLUDE PMF_FORM_UPDATE_UPD_OBJECT_I1
-* This is pmf_form_update_upd_object_i1.fex
CHANGE_ID = 'pmfadmin' ;
UPDATE_DATE = DT(2010/05/04 15:04:26.156) ;
ON MATCH UPDATE VARIABLE_VALUE CHANGE_ID UPDATE_DATE
ON NOMATCH REJECT
DATA
VARIABLE_NAME='RDBMS', VARIABLE_VALUE='DB2', $
VARIABLE_NAME='PMF_DB_OWNER', VARIABLE_VALUE='PMF', $
VARIABLE_NAME='PMF_DB_TABLESPACE', VARIABLE_VALUE='PMF_DATAMART_DATA', $
VARIABLE_NAME='PMF_DB_INDEXSPACE', VARIABLE_VALUE='PMF_DATAMART_INDEX', $
END
-RUN
(FOC1383) UNSUPPORTED DATETIME FORMAT FOR FIELD : UPDATE_DATE
0 TRANSACTIONS: TOTAL = 0 ACCEPTED= 0 REJECTED= 0
SEGMENTS: INPUT = 0 UPDATED = 0 DELETED = 0
BYPASSING TO END OF COMMAND

PMF 5.2.1 with HF1, W2003 Server, DB2 9.7.1

Any ideas?

It appears there is a situation in PMF 5.2.1 with DB2 where this can occur. We were able to reproduce and fix this in 5.2.2.

Are you doing this for a demo or are you at a customer site?

If a demo, then we recommend you take PMF 5.2.2 which is available this week.

If at a customer site, please contact CSS and we'll arrange a hotfix for 5.2.1 for your customer.

thanks
bjf

Bob, this is for a demo, so I'll install 5.2.2 when it becomes available.

Håkan

Bob,

any news on when 5.2.2 becomes available?

Håkan

We're down to one single issue to be fixed.

Know I'll regret this, but here you go:

Tomorrow May 13 at Noon/EST, we'll release it to the download site. Possibly it will take a little while before it appears, but that's the news.

As penance for taking an extra half day, I wanted to post the 5.2.2 New Features doc (to tease y'all) but FocalPoint won't let me upload the file - it's too big.

:-)