On August 27, between the hours of 8:30 and approx 11:30. something has caused our MF tpt's to go awry. MF team says nothing changed. DB team says nothing changed. the error we are now getting is:
TPT_INFRA: TPT04013: Error: opening temporary job script output file: "EDC5000I No error occurred." (0).
Job script compilation failed.
The tpt script is quite simple (for the test).
000001 DEFINE JOB load_L_LOCATION_STG(
000002 DEFINE OPERATOR DDL_OPERATOR
000003 TYPE DDL
000004 ATTRIBUTES
000005 (
000006 VARCHAR PrivateLogName = 'L_LOCATION_STG_ddllog',
000007 VARCHAR TdpId = @MyTdpId,
000008 VARCHAR UserName = @MyUserName,
000009 VARCHAR UserPassword = @MyPassword,
000010 VARCHAR logonmech = ldap,
000011 VARCHAR ARRAY ErrorList =['3807','2580']
000012 );
000013 STEP drop_error_tables_and_delete_data
000014 (
000015 APPLY
000016 ('DROP TABLE LDWM_STG_TEMP_DB.L_LOCATION_STG_W;')
000017 TO OPERATOR (DDL_OPERATOR () );
000018 );
000019 );
We are getting this error on all TPT's reagradless of which id runs them. this was not the case prior to Aug 27th.
Our MF security is handled by Top Secret application.
This same tpt script also runs perfectly from a linux platform
ANY SUGGESTIONS OUT THERE? we are at a complete loss.
one thing our MF folks did was chagne the UID for the prod users and jobs began running successfully, but some spardically failed with different message. odd thing is the exactsaem job may run just fine 3 times in a row then fail, then fail 2 times, run fine 1, faile again, etc....
Forums: