Page 1 of 1
could not attach to project Status code = 69
Posted: Thu Jul 26, 2001 12:58 pm
by admin
/ > dsjob -lprojects
Status code = 69
thanks and regards
Sudhir Mahendru
GTS/APHO-ITA/CA$H/IDMS-Datawarehouse
(65) 423-7449
--
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Posted: Thu Jul 26, 2001 2:44 pm
by admin
Sudhir,
Start with the obvious. Check your login user name and passed word are correct and that the caps lock is not on. After that check the that the name of the host system is correct on the login box. Failing this, is the server machine switch on and running with out any problems.
Regards
Adele McClue
-----Original Message-----
From: Sudhir Mahendru [mailto:
sudhir.mahendru@db.com]
Sent: 26 July 2001 13:58
To:
datastage-users@oliver.com
Subject: could not attach to project Status code = 69
/ > dsjob -lprojects
Status code = 69
thanks and regards
Sudhir Mahendru
GTS/APHO-ITA/CA$H/IDMS-Datawarehouse
(65) 423-7449
--
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Posted: Fri Jul 27, 2001 6:39 am
by admin
One of the many problems with dsjob is that its exit status is a single byte. So you dont get to see the whole error code. So 69 could be 69, 325 (256 + 69), 581 (512 + 69), and so on. You just dont know.
In the manual (Server Job Developers Guide) it states explicitly that dsjob is intended ONLY [my emphasis] as an example of how to use the DataStage C API.
Avoid dsjob wherever possible, and prefer DataStage job control routines.