11.07.2015 Views

Upgrade Guide - Prolifics

Upgrade Guide - Prolifics

Upgrade Guide - Prolifics

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

All ApplicationsTable 5-4 JPL (Continued)AreaunloadsqlNotesAn error is now generated when unload is issued for a file which was notpreviously loaded. Use call sm_jplunload ... to restore JAM 5 behavior.Obsolete. Use dbms sql instead.Table 5-5 ScreensFeatureCircular arraysCursor up/downField function flagsGroup navigationGroup function flagsMenus with controlfieldsMenus with return codesNotesArrowing down past the last occurrence places the cursor in the firstelement and displays the first occurrence there. Arrowing up past the firstoccurrence places the cursor in the last element and displays the lastoccurrence there. JAM 5 did not reposition the cursor.JAM 7 positions the cursor at the end of existing data by default whenentering a widget. To restore JAM 5 behavior, set IN_RESET =OK_NORESET in the set up file or call sm_option.K_KEYS always set to K_NORMAL on K_ENTRY.In JAM 7, TAB and BACK position the cursor to the next field by default.To restore JAM 5 behavior, call sm_key option and set the TAB and BACKkey bits to VF_GROUP | VF_CHANGE.The MDT bit is not set when a member is selected. K_KEYS is always setto K_NORMAL on K_ENTRY.Control fields are replaced by the control string property. There are twopossible conversions via f5to6. The first is to use f5to6 -5 to retaincontrol field functionality via the Release 5 widget type. The second is touse f5to6 -c to set the Control String property from the control field data,provided that its number of occurrences matches that of the menu field.Code that modifies the control fields must be changed to call property APIfunctions.To push back a key, call jm_keys from the control string property.<strong>Upgrade</strong> <strong>Guide</strong> 5-7

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!