STMS not showing transports in Production Queue

[Former Member]

Hi Again

I have two as400's where I have just setup 2 instances i.e dev and tst on the one as400 (server name saptst01) and I have setup the prd instance on the other as400(server name sapprd01).My transport domain controller sits on saptst01. on instance tst.

I have noticed that when i transport from dev thru to prd. it shows in the queue on tst but not on Prd.

I think my problem is that my prd instance is looking at usr/sap/trans on the local machine i.e sapprd01 and not saptst01.

At the moment its not a train smash, as i can just copy the cofile and data file on to the lcoal sapprd01 trans directory and then add it to the buffer.

For future, i Need to fix it. I saw a note "385498 AS/400: Error in the TPPARAM"

where it tells me to add a lnk.

Do i add a link on the sapprd01 machine or the saptst01 machine and do I do the ffg:

ADDLNK

OBJ('/QFileSvr.400/<AS400>/sapmnt/trans)

NEWLNK('/usr/sap/trans')

Will appreciate any help

[Former Member]

All the help was very helpful

Thanks.

[Former Member]

Hi Guys

The Main ting is that the symbolic link wont work if you ont create the directory structure on the as400 i.e

Create directory on os level '/QFileSvr.400/zasaptst

[Former Member]

Hi Guys

I have done what you suggested But it give me the ffg error message

"Object already exists. Object is usr/sap/trans."

I renamed trans to trans1. but after doing the addlnk again, and trying to access the directory, it gives me the ffg error message

" Object not found. Object is /usr/sap/trans."

Any suggestions would be helpful

[Former Member]

Hi

Appreciate teh feedback. Just need to know where do I create the link i.e

Do i add a link on the sapprd01 machine or the saptst01 machine and do I do the ffg:

ADDLNK

OBJ('/QFileSvr.400/<AS400>/sapmnt/trans)

NEWLNK('/usr/sap/trans')

Since my Transport directory is on the sapstst01 machine.

[Former Member]

Hi Morga,

Run it from your sapprd01 machine

ADDLNK

OBJ('/QFileSvr.400/saptst01/sapmnt/trans)

NEWLNK('/usr/sap/trans')

Currently on sapprd01, /usr/sap/trans might point to local /sapmnt/trans.

Please do consider Volker's suggestion, it is the best practice to have /usr/sap/trans on the production server.

Best regards,

Victor

[Former Member]

Hi Morga,

yes, this would fix your immediate issue.

But, you should then think on moving the physical transport directory to production, because the import is about 2 times faster on the local server compared to the remote server and you might want to reduce downtime for Support pack installations on production ...

(the domain controller could just stay where it is)

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de