An useful script

-



I develop T24 component and my browser is hosted in Jboss. The problem in Jboss is that if I change something in a routine or in a version or enquiry I have to restart the "jbase_agent"s. If not the changes won't take place in the browser immediately.
For this i have to use several unix commands to kill the agents. To simplify this i created a simple script. You need to compile this as a Program in your jbase server environment and run. This program is self explanatory.

PROGRAM JK2
$INCLUDE T24.BP I_COMMON
$INCLUDE T24.BP I_EQUATE
CRT "INPUT PORT NO"
INPUT Y.PORT
IF Y.PORT NE "" THEN
Y.EXC.CMD = "SH ps -ef | grep ":Y.PORT:" | grep -v grep | awk '{print $2}' | xargs kill"
EXECUTE Y.EXC.CMD
Y.EXC.CMD = "SH nohup jbase_agent -p ":Y.PORT:" &"
EXECUTE Y.EXC.CMD
END ELSE
CRT "INVALID PORT NO"
END
STOP

This program will kill all the running jbase_agent processes and start a new one in the background. This will save some time during the development.

Comments

Post a Comment

Popular posts from this blog

Local Ref Master

-
Image
When local reference field is added for an application, the same field is added to all the applications for which the field "Local Ref Master" in FILE.CONTROL record is set to the current application name. For example the applications AA.ARR.CUSTOMER, AA.PRD.CAT.CUSTOMER, etc... For the application AA.ARR.CUSTOMER, the Local Reference Master is AA.PRD.DES.CUSTOMER. If we try to attach a LT to AA.ARR.CUSTOMER directly the system will throw message as "Application uses local table of AA.PRD.DES.CUSTOMER". Only way to attach a LT to AA.ARR.CUSTOMER is to attach the LT to the master file.
Read more

SQL queries in JBase

-
The query Language of Jbase is really restrictive. Data analysis and comparison between two table is not possible without the use of spreadsheet software. I recently came to know that Jbase is providing a command called SQLSELECT through which you can actually issue SQL query command directly on Jbase tables. A sample would be like SQLSELECT * FROM FBNK.ACCOUNT WHERE SHORT_NAME LIKE '%PETER%' AND CATEGORY = 6601 Limitations: The command though have serious limitations such as  The table you query should not have dot charecter for example you cannot query FBNK.CUSTOMER.ACCOUNT with this command. But there is a workaround for the above drawback. Make a copy of the VOC record FBNK.CUSTOMER.ACCOUNT into a new one without ID in its ID. For Example: COPY FROM VOC FBNK.CUSTOMER.ACCOUNT,FBNK.CUSACC SQLSELECT * FROM FBNK.CUSACC; will work. The field name should not have dot character. You can overcome this by changing the dot character to underscore. For...
Read more

Current Variables in T24

-
CURRENT VARIABLE Introduction In addition to the system common variables that can be used in ENQUIRY and VERSION there is a feature where the user can populate a variable of their own and use it later. There are now a series of new system variables and a much wider option for users to create and use their own which are: CURRENT.CUSTOMER CURRENT.ARRANGEMENT CURRENT.EXTERNAL.USER These may be set on login by an external user and cleared when they logout. This means that ENQUIRY & VERSION can be tailored to accept the content of the variable instead of forcing a user to enter their own customer number or arrangement etc. Similarly in VERSION you can now default a field content by using the !CURRENT.CUSTOMER to populate a customer field with the current content of the variable. So the variable could be set in one Enquiry and used in either another Enquiry linked to it; or via VERSION to populate fields in an application triggered from the Enquiry. Note: ...
Read more