COB Question

Hello mates,

After start.tsm - debug, I got the following error :

START.TSM -DEBUG
tSA 1 -DEBUG
Error!! Cannot start COMO. Error number 22 creating file C:\MBR08\BNK.RUN\&COMO&\tSA_1_20092511_16:23:53
Agent 1 started 25 Νοε 09 16:23:53
Agent's Process id 5244
Running on server ‘«œ­˜¤¦ª-PC PortNumber 3

Does anyone has idea about it?

Regards

Hi,

DO the following

1.Issue the command: CLEAR.FILE F.TSA.STATUS
NB: Its F.TSA.STATUS and not F.TSA.SERVICE


2. Issue the command: ps -ef and check for the process id using TSM.
Issue command: WHERE(
this gives you the user,
issue command : LOGOFF xxx
where xxx is the user displayed from command WHERE(

3. Logout from the session and login

4. Then issue your tSA TSM -DEBUG,
It should work now.

Hi my friend and thanks for the info...

Unfortunately , ps -ef is unable to execute from jbase prompt, but apart of this, I tried with LOGOFF from the PID which I got from WHERE ( and then sign in again but nothing happened...I have the same message..."cannot start COMO"...

Anyway, thank you very very much Glojoy

From your response, your tsa service actually starts, its the COMO file that is unable to get created, right?

Do this
shell to the unix prompt and check the permission on the directory where the &COMO&\tSA_1_20092511_16:23:53 resides.(i.e ls -lrt ?COMO?).
Check for the ownership, it must be own by the user used in logging into the environment.

Also check for space availability(it could be there's no more space)

backup the tSA_1_20092511_16:23:53 file under &COMO&


Issue jsh to go back to jbase prompt

Now try re-creating tSA_1_20092511_16:23:53 from within jbase see if it's possible.

CREATE.FILE &COMO& tSA_1_20092511_16:23:53 TYPE=J4

Yes, the problem it comes up after I am trying to start the Service Manager from jBASE...I mean, after I type the START.TSM –DEBUG...
The error is
jsh R0800 ~ -->START.TSM -DEBUG

START.TSM -DEBUG
tSA 23 -DEBUG
Error!! Cannot start COMO. Error number 22 creating file C:\MBR08\BNK.RUN\&COMO&\tSA_23_20092711_16:55:55
Agent 23 started 27 Νοε 09 16:55:55
Agent's Process id 2420


I am trying to do this from JBASE , local host on R8...so , I cannot run commandes like ls-lrt...
Anyway, I really appreciate your help Glojoy...

Have a nice week-end

You can run unix commands, use SH first :-

SH ps -ef | more

Thanks Wayne, but I think I cannot...

jsh R0800 ~ -->SH ps -ef | more

'ps' is not recognized as an internal or external command,
operable program or batch file.

I don'know If I am typeing something wrong...

first type SH <enter>
and your command ps -ef | more <enter>

jsh R0800 ~ -->SH
SH
jsh R0800 ~ -->ps -ef | more

[3] Unable to execute program 'ps -ef | more'
jsh R0800 ~ -->

Bala_gates,
Thanks for the info, but unfortunately as you can see above, it does not work.

type small letter sh instead of "SH"

and the rest are same

Hi bala_gates

jsh R0800 ~ -->sh
sh
jsh R0800 ~ -->ps -ef | more

[3] Unable to execute program 'ps -ef | more'
jsh R0800 ~ -->

I think , you cannot use UNIX commands from jBASE prompt...at least from localhost...

hi stefano,
just to share more light to ur issue..am using RO8 too on my system
and i do run cob as well but to my view can you try to check the agent
id you are trying to start maybe it has already been ran?
becos ur error shows that the agent was started correctly and gives u the agent id
try this ....stop both the services,TSA.SERVICE ..COB and TSM service
logout from the system and login again re-start the services
and pick the current agent...

sorry u can not execute all those command in jBASE okay!!!
pls revert back ASAP..

NB;u can mail me on This email address is being protected from spambots. You need JavaScript enabled to view it.

jsh R0800 ~ -->START.TSM -DEBUG

START.TSM -DEBUG
tSA 1 -DEBUG
Error!! Cannot start COMO. Error number 22 creating file C:\MBR08\BNK.RUN\&COMO&\tSA_1_20091208_15:42:02
Agent 1 started 08 DEC 09 15:42:02
Agent's Process id 4768

Hi soliu@t24peers (what user name is this??? :-) )

Before I start running COB always I stop the COB and TSM...before I start them again... Once again the same problem comes up...Something relative by the COMO...

Anyway, thanks for your help

the user name u mention is wt i'm planning to name my
t24 company soon!!!
anyway pls can u show wt u have in the folder ....bnk.run/&como&?
to be able to analyze the issue...
tnx...

Dear Stefano,

To get to the root of issue,finally captured whre the error was caming from pls take note of this....
cannot start agent 1 (tSA 1 -DEBUG). This is because the TSM automatically uses this.

Also, the agents available for use would have been specified when the command START.TSM -DEBUG is issued, SEE BELOW:.

Manually launch tSA 2 BNK/SC.CORPORATE.ACTIONS
Manually launch tSA 3 BNK/AM.SC.MOVEMENT
Manually launch tSA 4 BNK/CR.CAMPAIGN.PROCESSING
Manually launch tSA 5 BNK/OFS.MESSAGE.SERVICE
Manually launch tSA 6 BNK/PRINT.OUT
Manually launch tSA 7 BNK/PRINT.OUT
Manually launch tSA 8 BNK/SWIFT.OUT
Manually launch tSA 9 BNK/SWIFT.OUT
Manually launch tSA 10 BNK/CR.OPPORTUNITY.PROCESSING
Manually launch tSA 11 BNK/SEC.OPEN.ORDER.SERVICE
Manually launch tSA 12 COB
Manually launch tSA 13 COB
Manually launch tSA 14 COB
Manually launch tSA 15 BNK/AM.DYNAMIC.MODEL.SERVICE
Manually launch tSA 16 BNK/AM.DYNAMIC.MODEL.SERVICE
Manually launch tSA 17 BNK/CR.PROCESSING
Manually launch tSA 18 BNK/CR.PROCESSING
Manually launch tSA 19 BNK/CR.PROCESSING
Manually launch tSA 20 BNK/CR.PROCESSING
Manually launch tSA 21 BNK/CR.PROCESSING
Manually launch tSA 22 BNK/CR.PROCESSING
Manually launch tSA 23 BNK/CR.PROCESSING
Manually launch tSA 24 BNK/CR.PROCESSING
Manually launch tSA 25 BNK/CR.PROCESSING
Manually launch tSA 26 BNK/CR.PROCESSING
Manually launch tSA 27 BNK/PW.MAPPING


I hope this is clear.dont hesitate to revert back

Rgds..

Hi my friend ,

The steps which I've make in order to run COB are the following:
START.TSM –DEBUG from jBASE in order to start the service manager.

After this immediately I get the error for COMO.

If I ignored the message for COMO and continued by tsa2 the agent stoped.

So, what you said above for agents 2....27 for me is the next step which I cannot executed.

By the way...hope you will establish your own company soon and wish you Good Luck for this.

:-)

Hi friend,

I hope you have some technical manuals u going through? if nt pls kindly
ask for so we can send ....
it's seem u don't understand the message at all....

listening very attentively..u don't have to start cob with agent 2
what u need to do after started ur TSM, COB services correctly u then
go jbase isuse the command START.TSM -DEBUG ...it will show the below
msge...Manually launch tSA 10 BNK/CR.OPPORTUNITY.PROCESSING
Manually launch tSA 11 BNK/SEC.OPEN.ORDER.SERVICE
Manually launch tSA 12 COB
Manually launch tSA 13 COB
Manually launch tSA 14 COB
then u will pick one of ths tSA 12 COB ...jsh tSA 12 if u press eneter
it wuld start these agent 12 and run ur cob
u can use the procedure on the other agent as well but u can not start tSA with 2 pik from those tSA12,tSA 13 and tSA 14..
hope u comprehend!!!!!!!

Hi,

From your error message, I guess that the USER does not have proper rights to create a file in the C:\MBR08\BNK.RUN\&COMO& folder. Could you right-click on the &COMO& folder and check whether the localhost user has been provided full rights under Security tab in Properties window?

Regards

Hi Big_BJ,
Thanks a lot for the info, I add my localhost user in the COMO file with full rights but still I get the same error message.
Is ok guys, I can run COB but I get this message, don't waste more our time, we will leave it as it is, is not important.

Soliu@t24peers and all the others mates, thanks a lot for your replies, let's close this subject now and if at the future someone find something, here it is the post for share the info with us.

2010 Warm wishes to all of you and your families for a Happy New Year...is coming in 12 hours from now...!!!

Cheers

Its bug on R8. Windows does not recognize file name with colon (tSA_2_20100201_10:27:49 )

Unix works fine

In some later patch it has been changed to dash.

I'm trying to get hold of this patch myself.