You've brought up a few different issues during this discussion thread. The issues I see are:
1 - failure to dump a database log via the sp_dumptrans stored proc because said proc does not exist in your ASE dataserver instance; you're now having problems trying to create the sp_dumptrans stored proc in your ASE dataserver instance
2 - wanting to a) shrink a database's log space allocation and/or b) shrink the size of a log device out in the OS [you've mixed some terminology - understandable for someone new to ASE - so not 100% sure what the real issue is]
3 - you've been able to manually dump the tran log for the QAS database using the 'dump tran' command
----------
The following is an attempt to address item #1 and only item #1 ...
- you tried to dump a database's transaction log via a stored proc named 'sp_dumptrans'; this failed because the sp_dumptrans stored proc had not been loaded into your ASE instance [you need to load/create the sp_dumptrans stored proc in your ASE instance]
- you're trying to create the sp_dumptrans stored proc (by loading the sp_dumptrans.sql script) in the saptools database but this is failing because the saptools database is full [creating a stored proc requires adding rows to a few system tables including a system table called 'sysprocedures'; the error message is telling you there's no room to add records to the sysprocedures table]
In order to create the sp_dumptrans stored proc (ie, load the sp_dumptrans.sql script file) you have to either a) free up space in the saptools database or b) add space to the saptools database.
NOTE: I don't support SAP applications on ASE so I don't know if there's a SAP note for addressing your particular issue.
----------
Bret has provided a couple steps to address the space issue in the saptools database. However, from your responses I'm assuming much of what's been said in this thread hasn't made a lot of sense (ie, you're new to Sybase ASE) so, we'll need some more info if we're to provide you with the detailed steps to get the sp_dumptrans.sql script to load successfully.
a - log into your dataserver with isql: isql -SQAS -Usapsa -PWelcome12345 -w1000
b - run the following in your isql session:
use master
go
select * from syslogshold where dbid = db_id('saptools')
go
sp_helpdevice
go
use saptools
go
sp_helpdb saptools
go
sp_helpsegment logsegment
go
c - post the entire output from step #b to this thread (preferably as an attachment if you can otherwise in the body of a post); with this info we should be able to come up with a list of detailed steps to get some free space so the sp_dumptrans proc can be loaded into your saptools database