Client - Server Questions
1) What is the difference between Window And dialog?
2) What is Select char attribute?
3) What is the difference between view matching and view mapping?
4) How to debug the client code on PC?
5) What are the tools to test server code?
6) What is the limit on data transfer between client and server?
7) What are the different types of events?
Also look at the Set # 2 post for more questions.
8 comments:
For q1: Window has sizing borders. They are not available in a dialog.
You can provide menu and status bar in window but the same does not apply to a dialog.
System buttons like minimise, maximie and close can be available for window but only close button is made available for a dialog.
regards,
M V
For Q2: Select char attribue forms a part of your group view associated to a list or a dropdown box. Selecte char helps in selection of an item from the list or dropdown box. When you use a selection indicator, the Window Manager automatically places an asterisk (*) into the attribute.
you can use the selection indicator to preselect attributes in a list box
Manish V
For Q3:
View matching is used to match the views of the called (used) action block or Pstep to the views of the calling procedure step or action block.
If you do not want to match all the views, you can match to .
Problem occurs with data passing from one proc step/AB to another proc step/AB if view matching is not performed properly thus resulting into incorrrect output.
View Mapping is done at GUI/Window level.
View mapping causes the values of attribute views in the export view to be copied to the corresponding attribute views in the import view.
View mapping minimise the efoort of checkin whether the views for all the objects on a window are matched to each other or not.
Data passing is hindered if views are not mapped properly.
Adding one more point, mainly we have the data on the window in export view. To make the data available in import view we use view mapping at window level.
# TO test the client code we use diagram trace utility. DTU is a tool provided by CA to do test our client procedures in the local machine.
We trigger the tran code of window manager of particular procedure step and make the code available in tool(DTU) and start testing.
# To test the Server procedure we use DTF, Diagram trace facility in mainframe(back-end).
Before we do the testing we need to have the generated code both client/server with Trace option(for client in toolset -> make the option Trace 'y', for server in encyclopedia -> select/enable the debug option).
Keep in mind that we need to have the defined library(load, source code) in internal library under encyclopedia.
Once we do the new copy in region(CICS) we can trigger the server and make code available in region and start testing.
32k limit for data transfer
#7. We have different events for window,
Open
closeleftmousebtndown
leftmousebtnup
rightmousebtndown
rightmouseupbtnup
activated
deactivated
mousemove
winmove
winresize
Thanks for the answers
Post a Comment