istool - custom path
Moderators: chulett, rschirm, roy
istool - custom path
We have V8.1.0.1 [with fixpack1], I am able to build a package from GUI, but not able to find the package in the server
How can I fid the location of the file [ tried find / -name "<package_name>" -print #couldn't find]?
Is it possible to give the location of the file while building (or) do we need to configure anything in the server for this?
Thanks for all your replies
Prasad
How can I fid the location of the file [ tried find / -name "<package_name>" -print #couldn't find]?
Is it possible to give the location of the file while building (or) do we need to configure anything in the server for this?
Thanks for all your replies
Prasad
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Try
Look first in the directory from which you executed istool.
Code: Select all
find / -name '*package_name*' -print
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Thanks, I am able to configure the path as you suggested, the defaut path was //istoolBuild.
When I created a new package in /tmp, the file was created as a root user and root group is this the default behaviour? It would be difficult for regular users to delete the file externally (i.e. from UNIX)? Currently we can delete it from IS Manager tool.
Thanks
Prasad
When I created a new package in /tmp, the file was created as a root user and root group is this the default behaviour? It would be difficult for regular users to delete the file externally (i.e. from UNIX)? Currently we can delete it from IS Manager tool.
Code: Select all
-rw-r--r-- 1 root root 66442 May 25 12:30 /tmp/Test.pkg
Prasad
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Yes our services run with the root id. To resolve the client hung up issue we are starting the services with root id. Is there any best practice, with which id to start the services?
Is there possible to have any option for IS Manager for saving the packages with the individual user id's in server?
Thanks
Prasad
Is there possible to have any option for IS Manager for saving the packages with the individual user id's in server?
Thanks
Prasad