0% found this document useful (0 votes)
2K views26 pages

TAFJ - Working With Design Studio - R16

This document provides instructions for invoking and debugging T24 programs within Design Studio. It describes how to configure and run T24 programs as well as debug them locally or remotely. It also discusses using tools like the JED wizard to edit data records and files, the lock management view, and the JQL-SQL-OFS editor.

Uploaded by

adyani_0997
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2K views26 pages

TAFJ - Working With Design Studio - R16

This document provides instructions for invoking and debugging T24 programs within Design Studio. It describes how to configure and run T24 programs as well as debug them locally or remotely. It also discusses using tools like the JED wizard to edit data records and files, the lock management view, and the JQL-SQL-OFS editor.

Uploaded by

adyani_0997
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 26

TAFJ - Working with Design Studio - R16

TAFJ - Working with Design Studio - R16


TAFJ - Working with Design Studio - R16
You can invoke T24 classic inside Design Studio.
1. Click on Run menu -> Run configurations (Alternatively use the Run as button in
the toolbar). Run configurations can be used to launch any T24 ‘Program’ on the
console.
2. Right click on BASIC program -> New
3. Give a name for the Basic program – in the snapshot EX… it can be any name
4. In the Launch options, specify the actual routine name (EX) to run in the Program
textbox and the project where the routine is available.
5. Check the Eclipse Console check box. The default eclipse console port is 9994.
6. Click on Run.

Alternatively right click on the T24_BP\EX and choose Run as .. Basic program. EX
appears in the Run as … and Debug as.. Menu automatically. The same is true for
any routine run in TAFJ.

TAFJ - Working with Design Studio - R16


Click on the T24 Runner tab. You can provide the login credentials to login to T24
classic.

TAFJ - Working with Design Studio - R16


If you want to input OFS requests, then we need to launch tSS. Like EX, tSS is also a
T24 ‘Program’.

1. Click on Run menu -> Run configurations (Alternatively use the Run as button in
the toolbar). Run configurations can be used to launch any T24 ‘Program’ on the
console.
2. Right click on BASIC program -> New
3. Give a name for the Basic program – in the snapshot tSS it can be any name
4. In the Launch options, specify the actual routine name (tSS) to run in the Program
textbox and the project where the routine is available.
5. Give the Argument as TELNET which is the OFS.SOURCE record of type
TELNET
6. Define breakpoints in the routines to investigate
7. Click on Debug.

Alternatively right click on the T24_BP\tSS and choose Debug as .. Basic program.
tSS appears in the Run as … and Debug as.. Menu automatically. The same is true
for any routine run in TAFJ.

TAFJ - Working with Design Studio - R16


OFS request :
ACCOUNT,/I/PROCESS,INPUTT/123456,,CUSTOMER=600001,CURRENCY=CHF,C
ATEGORY=1001
To run COB launch the T24 Program START.TSM and tSA. Remember to give the
Arguments as shown. For tSA since we will not know until runtime the agent number,
we need to pass the argument as <prompt>

These two properties decide where the &COMO& is created.


temn.tafj.runtime.directory.current = <tafj.home>/UD
temn.tafj.runtime.directory.como = <temn.tafj.runtime.directory.current>/&COMO&

TAFJ - Working with Design Studio - R16


TAFJ - Working with Design Studio - R16
It is easy to debug T24 on a remote machine from your machine. Lets say you want to
launch EX on 10.93.7.179 and debug the T24 area on that machine. Execute the
tClientConsole command on the remote machine. In your Debug(/Run) Configuration,
check the checkbox for Remote client. Provide the IP address. The default client
console port is 9993. Now when you launch EX in Design Studio on your machine, the
I/O is redirected to the remote client console and will appear there. The user at the
remote machine can recreate the problem there and you can debug on your Design
Studio by defining break points where needed.

You can also launch tSS, BROWSER.LISTEN in the same fashion to debug browser
and OFS requests posted on a remote machine.

[Note: Remember to uncheck Eclipse Console in the Debug/Run configuration of EX


for evident reasons]

TAFJ - Working with Design Studio - R16


You need to create a USER credential to access DBTools commands from console.
Run from TAFJ_HOME/bin:
tAddUser.bat or tAddUser.sh depending on the platform.
Username – preferred user name
Password – preferred password
Once the user is created, you can login and You can start accessing
the DBTools and tJed wizard commands.
Right clink on project -> select DBTools Login option
Supply valid User credentials
Invoking the Jed Wizard
Right click on your TAFJ Project and in the drop down menu, select “Invoke Jed
Wizard”
Now you will see the screen below, enter a table name and record that you want to
see (example, FBNK.CURRENCY and RecordId GBP). Click Finish.
It will open a JED Data editor for the requested record. If you have ticked option “Show
column names” they would be displayed whenever available in T24.
Once the editor is opened, it should look like the snapshot.
1. Double click within a cell to edit it.
2. Right click on a field to insert field, multi-values and / or to insert subvalues.
3. Right click on a field to delete it.
The contextual menu for point no 2, changes depending on the type of the field as
seen in the snapshot where the right click was done on a single value and an
associated multivalue field. An asterix (*) appears on the tab when the record is
modified.
Two actions are available in the toolbar whatever the status of the record is:
Synchronize the editor with the record in the database
Delete the record (you will be prompted for confirmation, then upon confirmation this
action cannot be undone).
Once the record has been modified all actions become available in the toolbar. It’s
then possible to:
Revert the modification

TAFJ - Working with Design Studio - R16


Save the modification

TAFJ - Working with Design Studio - R16


Editing a data file
A .d file could be opened with the JED editor by double clicking on it. It could be then
edited the same way as mentioned previously.
The only difference is about the toolbar which has a different purpose. It’s possible to
synchronize the file content with the database and to upload the file content into the
database.

TAFJ - Working with Design Studio - R16


Extract and Load Data
By right clicking on a .d file in the package explorer, it is possible to directly extract it or
to load it into the database.
When clicking “Extract from the database” the wizard in the snapshot will be displayed.
You can view the result in the console

TAFJ - Working with Design Studio - R16


You can open the record by double clicking on the F.CURRENCY!USD.d file. Edit the
description field and save the record.

TAFJ - Working with Design Studio - R16


Load Data
The extracted *.d record can then be edited by double clicking on it as shown
previously. Right click on the *.d record in the package explorer and choose ‘Load in
Database’ option. The wizard shown in the slide is displayed. Click on Finish
The output is displayed on the console.
By default a record loaded in T24 requires a manual authorization, thus it will be
uploaded in the corresponding $NAU table.

TAFJ - Working with Design Studio - R16


An eclipse view is available to manage the locks handled by the TAFJ lock manager.
Right click on the TAFJ project and choose Lock Management View.
Use the view either by refreshing it periodically whenever needed or start an automatic
refresh with a refresh interval in seconds specified.
Once the locks are displayed select the one that belongs to release them if needed. To
release a lock, select it by clicking on it and use the “Release selected lock button”.
You could release all your locks at the same time by clicking “Release all locks”. You
could also see locks that belong to other users, or held by external eclipse process,
these lock info display is greyed and can’t be released.
If you start the automatic refresh, you will be able to stop it with the button enabled in
the toolbar.

TAFJ - Working with Design Studio - R16


An editor is available to launch JQL, OFS and SQL commands. Right click on the
project and click on JQL-SQL-OFS Editor
The default mode is JQL and allows executing JQL statements on a running database.
Click on the drop down to view the other modes
SQL – for executing SQL statements on a database which is running
JQL2SQL – to translate JQL commands to corresponding SQL commands. This is
only a translation editor and the commands will not execute.
OFS – to pump OFS requests provided the database is running and the reference to
the precompiled T24 jars exists
SUBROUTINE – Does a subroutine call (CALLAT) on application server deployments
The command line is used to type the command for execution. To execute a command
type it on the command line then type “Enter”. The display result set of the command
USAGE typed at the command line can be viewed in the result panel. USAGE
command lists valid commands for the mode selected (JQL/SQL). It could be copied to
the clipboard to be paste somewhere else. To copy a result or part of it, select the
lines of your interest and right click on the result panel, a
“Copy” option appears.
In SQL mode, in case of a SELECT, the first 200 rows of the result set get fetched by
default. This default fetch size of 200 can be modified by using the check option
“Fetch all rows” to fetch all rows. This may lead to a memory overhead.
The command history panel retains a memory of the last 10 commands executed at
the command line. Use the X button on the top right hand side corner to clear history.
History information is shared across all users.

TAFJ - Working with Design Studio - R16


In the snapshot shown, OFS mode is selected and the output of an OFS request is
displayed.

To execute OFS requests specify the OFS source, default is GCS. If you indicate a
split response, then the OFS response is splitted into separate lines according to the
separator. The default OFS response line splitter is the “,” separator. OFS request can
be executed on a remote server installation by selecting the hostname checkbox and
providing server hostname (could be localhost) and the application server port for
HTTP request.

TAFJ - Working with Design Studio - R16


The SUBROUTINE mode performs a subroutine call (CALLAT) on application server
deployments. Supply the server hostname (could be localhost) and the application
server port for HTTP request (along with the offset if there is one).
The request format, as presented below, is :
[SUBROUTINE.NAME]<FM>[NUMBER OF PARAMETER]<IM>[PARAM VAL
1]<IM>[PARAM VAL 2]…

TAFJ - Working with Design Studio - R16


GOSUB Graph
The GOSUB graphs displays the dependencies between the labels within the routine.
When editing a basic file the Gosub graph for this file will be automatically generated
and updated according to the basic code change. Double clicking on a graph node will
redirect you to the corresponding label in the basic editor.
When you have an important number of node levels, you could tune the node size to
have the graph fit the screen.
You could also switch between different nodes layout.

TAFJ - Working with Design Studio - R16


Clean a project, will:
Delete all java files
Ask if you want to delete all classes files
To Clean all project or one specific project, from the main workbench window, click
Project > Clean
Choose if you want to clean all project or select the project(s) you want to clean.
Choose if you want to delete classes

TAFJ - Working with Design Studio - R16

You might also like