RAMP-TS Guide
Table of contents
-
RAMP-TS Guide
- How to Get Started with RAMP
- What's New
- Licensing Requirements
- Installation and Configuration
- Starting RAMP
- Concepts
- Modernization Issues
-
Tutorials for RAMP Windows
- Before You Use the Tutorials
-
RAMP-TS001: Creating a Basic Prototype of the Modernized Application
- Application before Modernization
- RAMP-TS001 Step 1. Create the Application Prototype
- RAMP-TS001 Step 2: Modify the Code Tables Prototype
- RAMP-TS001 Step 3: Examine the Employees Prototype
- RAMP-TS001 Step 4: Prototype End-User's Access to Employee Information
- RAMP-TS001 Step 5. Visualize the Filters
- RAMP-TS001 Step 6. Validate the Basic Prototype
- Summary
- RAMP-TS002: Rapidly Modernizing Complete Application Segments
- RAMP-TS003: Creating a Data Filter for Employees
- RAMP-TS004: Naming and Classifying the Employee Screens
- RAMP-TS005: Reviewing Design
- RAMP-TS006: Snapping in a Basic Inquiry Screen
- RAMP-TS007: Snapping in a Data Entry Function
- RAMP-TS008: Changing Inquiry Screen to Update Mode
- RAMP-TS009: Tracing Navigation
- RAMP-TS010: Using Special Field Handlers
- RAMP-TS011: Snapping in Shipped Documents Command Handler
- RAMP-TS012: Snapping in Shipped Notes Command Handler
- RAMP-TS013: Sending Instance List Data to Excel
- RAMP-TS014: Snapping RAMP Screens into the HR Demo Application
-
RAMP-TS015: Understanding and Handling Screen Variations
- What is a 5250 Screen?
- RAMP-TS015 Step 1. Assigning the Same Name to Two Screen Variations
- RAMP-TS015 Step 2. Handling Different Screens with the Same Signature
- RAMP-TS015 Step 3. Creating Screen Variants
- RAMP-TS015 Step 4. Using Screen Variants in the Script
- RAMP-TS015 Step 5. Creating a Set of Screens (Advanced)
- Summary
-
Advanced Tutorials
-
RAMP-TSAD01: Using Buttons to Add Value to an Application
- About Buttons
- RAMP-TSAD01 Step 1. Enable Framework Buttons
- RAMP-TSAD01 Step 2. Name Fields to Be Copied on the DisplayEmployee Screen
- RAMP-TSAD01 Step 3. Add a Function to the Script for the DisplayEmployee Screen
- RAMP-TSAD01 Step 4. Call the Function in the ButtonClick Function
- RAMP-TSAD01 Step 5. Test the Buttons
- Summary
-
RAMP-TSAD02: RAMP-TS Event Handling Basics
- RAMP-TSAD02 Step 1. Add a Signal Button to the By Name Filter
- RAMP-TSAD02 Step 2. Make Your 5250 Screen Listen to the Signal
- RAMP-TSAD02 Step 3. Test Signaling from Filter to RAMP Screen
- RAMP-TSAD02 Step 4. Add a Signal Button to the RAMP Screen
- RAMP-TSAD02 Step 5. Make the Filter Listen to the Signal
- RAMP-TSAD02 Step 6. Signalling from a RAMP script to a VLF component
- Summary
-
RAMP-TSAD03: Special Field Handling
- RAMP-TSAD03 Step 1. Understand What Makes the Prompter Appear
- RAMP-TSAD03 Step 2. Being smarter with HANDLE_PROMPT()
- RAMP-TSAD03 Step 3. Handler Styles
- RAMP-TSAD03 Step 4. Generic Handler Association
- RAMP-TSAD03 Step 5. Generically Associating Date Fields with Date Picker
- RAMP-TSAD03 Step 6. Dynamic Handler Association
- RAMP-TSAD03 Step 7. Communicating with a Handler
- RAMP-TSAD03 Step 8. What to Do When Things Do Not Work
- Summary
-
RAMP-TSAD04: Redesigning the Screen Using aXes
- RAMP-TSAD04 Step 1. Get Started with aXes Designer
- RAMP-TSAD04 Step 2. Set up Styles
- RAMP-TSAD04 Step 3. Hide Repetitive Information
- RAMP-TSAD04 Step 4. Add a Tooltip
- RAMP-TSAD04 Step 5. Add a Drop-Down
- RAMP-TSAD04 Step 6. Organize Fields inside Group Boxes
- RAMP-TSAD04 Step 7. Add Up and Down Buttons to Subfile
- RAMP-TSAD04 Step 8. Hide Function Keys and Add a Picture
- RAMP-TSAD04 Step 9. Add a Hyperlink
- RAMP-TSAD04 Step 10. Test the Redesigned Screen
- RAMP-TSAD04 Step 11. Remove the Screen Customization
- Summary
- RAMP-TSAD05: Using SHARED Properties and Functions
-
RAMP-TSAD06: Handling Multiple Screens on Multiple Tabs
- RAMP-TSAD06 Step 1. A Multiple 5250 Screen Scenario
- RAMP-TSAD06 Step 2. Name the Screens
- RAMP-TSAD06 Step 3. Classify the Screens
- RAMP-TSAD06 Step 4. Review and Understand the Targets List
- RAMP-TSAD06 Step 5. Using Multiple Command Handler Tabs
- RAMP-TSAD06 Step 6. Review and Alter Buttons and Function Keys
- RAMP-TSAD06 Step 7. Review the value you have added to the 5250 application
- RAMP-TSAD06 Appendix: Function UFRTS03
-
RAMP-TSAD07: Handling Multiple Screens on a Single Tab
- RAMP-TSAD07 Step 1. A Multiple 5250 Screen Scenario
- RAMP-TSAD07 Step 2. Making a Plan
- RAMP-TSAD07 Step 3. Putting the Screens on a Single Tab
- RAMP-TSAD07 Step 4. Enable Function Keys/Buttons and Add Required Scripting
- RAMP-TSAD07 Step 5. Defining the Exit Junctions and vHandle_NAVIGATETO scripting
- RAMP-TSAD07 Step 6. Testing and Debugging
- RAMP-TSAD07 Step 7. Fine Tuning
- RAMP-TSAD08: Screen Wrapper Basics
- RAMP-TSAD09: Screen Wrapper with a Subfile
-
RAMP-TSAD01: Using Buttons to Add Value to an Application
-
Scripting
-
Learning
- Anatomy of Scripts
- Scripts in a Classic Details Display
- Javascript Essentials
-
Using
- Interacting with Instance Lists in Scripts
- Scripting Pop-up Menu
- Updating the Instance List from RAMP screens
- Subfiles/Browselists
- Script Skeletons
-
Script Functions
- LOCK_FRAMEWORK Function
- UNLOCK_FRAMEWORK Function
- RESTART_LAST_NAVIGATION Function
- OVRSFLAUTOGUI Function
- AVSWITCH Function
- TRIM_RIGHT Function
- TRIM_LEFT Function
- SHOW_CURRENT_FORM Function
- SHOWSTATUSBAR Function
- TOSTRING Function
- TONUMBER Function
- SETBUSY Function
- CHECK_FIELD_EXISTS Function
- DROP_SPECIAL_FIELD_HANDLER Function
- SET_SPECIAL_FIELD_HANDLER Function
- GET_FORM_MESSAGE Function
- SCREEN Function
- HIDE_5250_BUTTONS() Function
- SHOW_5250_BUTTONS() Function
- COPYTOCLIPBOARD Function
- FATAL_MESSAGE_TYPE Function
- SETKEYENABLED Function
- SETVALUE Function
- Q_SETVALUE Function
- GETVALUE Function
- SENDKEY Function
- Q_SENDKEY Function
- CHECK_CURRENT_FORM Function
- Q_CHECK_CURRENT_FORM Function
- AVCLOSEFORM Function
- HIDE_CURRENT_FORM Function
- CURRENT_FORM Function
- SETCURSORTOROW Function
- SETCURSORTOFIELD Function
- ALERT_MESSAGE Function
- CLEAR_MESSAGES Function
- FATAL_MESSAGE Function
- MESSAGE Function
- AVSIGNALEVENT Function
- TRACE Function
- HANDLE_PROMPT Function
- NAVIGATE_TO_SCREEN Function
- Q_NAVIGATE_TO_SCREEN Function
- STRIP_LEADING_NUMBERS Function
- ADD_STRING Function
- STRING Function
- OVERRIDE_KEY_CAPTION_SCREEN Function
- OVERRIDE_KEY_CAPTION_ALL Function
- AVSAVEVALUE Function
- AVRESTOREAVALUE and AVRESTORENVALUE Function
- ADD_UNKNOWN_FORM_GUESS Function
- SET_HANDLER_CAPTION Function
- Framework Objects that Scripts Can Refer To
- User-Defined Script Functions
- Switching Off Recursion Checking
- When Are Scripts Reloaded so That Change Can Be Tested?
- Advanced Scripting
- Debugging
-
Learning
-
Screen Enrichment
- Hide screen titles in individual RAMP Screens
-
The HTMLAPI Scripting Object
- Using The HTMLAPI Scripting Object
-
HTMLAPI Usage Examples
- Implementing a Basic Standard Layout function
- Generically Modifying a Screen via the Standard Layout function
- Specifically Modifying a Screen via a Specific Layout function
- Adding More Capability to the Standard Generic Handler
- Modifying Subfile Headings
- Modifying Fonts
- Adding Images
- Things to watch out for
- What HTMLAPI functions are provided?
- Screen Wrappers
-
Programming Techniques
- Using Function Key Descriptions to Condition RAMP Buttons
- Handling a Single Screen which Shows Multiple Modes
- A Command Handler Tab with Many 5250 Destinations
- Advanced Prompting
- A RAMP Design Approach Using a Single Junction Point (SJP)
- Using HIDE_CURRENT_FORM to manage access to command handler tabs
- Multilingual RAMP Applications
- Troubleshooting
-
Frequently Asked Questions
- How to tell in a RAMP-TS script what theme is being used?
- How is a Framework associated with RAMP-TS or RAMP-NL?
- I have made a mistake in classifying a screen. How do I change the classification?
- How do I differentiate two screens which have the same name?
- How can I use web browser windows from RAMP scripts?
- How can I get the message from the bottom of the current 5250 screen into my RAMP script?
- How do I handle RA (Auto Record Advance) fields?
- Why should the F12=Cancel and F3=Exit buttons and function keys be disabled on every 5250 screen?
- Do I have to identify and script every 5250 screen in my application to modernize it?
- How can I get the RAMP tool to assign a fixed session?
- How do I make my scripts work in multiple partitions?
- Can you add in your own functions to the scripts?
- How do I stop break messages in aXes 5250 sessions?
- Appendix
- Where and how are my RAMP-TS screen identifications kept?