Global restrictions in LMSCONV compared to LMS:
No creation of delta-stored members
No structured output, i.e. no output to S variables
No modification of library and type attributes
No support for a start file
The following LMS statements are not supported:
ACTIVATE-USER-EXIT BEGIN-MAKE CALL-EDT COMPARE-ELEMENT DEACTIVATE-USER-EXIT EDIT-ELEMENT EXECUTE-SYSTEM-COMMAND FIND-ELEMENT MODIFY-ELEMENT-PROTECTION MODIFY-LIBRARY-ATTRIBUTES MODIFY-TYPE-ATTRIBUTES PROVIDE-ELEMENT REORGANIZE-LIBRARY RESET-Anweisungen RETURN-ELEMENT SHOW-STATISTICS
The following table shows the syntax restrictions compared to LMS:
Statement | Restriction |
---|---|
| No *HIGH,*INCR,BASE,STORAGE-FORM for TO-ELEMENT |
| ./. |
| No selection via BASE for ELEMENT |
|
|
| No selection via BASE for ELEMENT |
|
|
| No selection via BASE for ELEMENT |
| No STORAGE-FORM for ELEMENT-ATTRIBUTES |
| No selection via BASE for ELEMENT |
| No selection via BASE for ELEMENT |
| No EDT(...) for TEXT-OUTPUT |
|
|
| No PROTECTION |
| No selection via BASE for ELEMENT |
| No selection via BASE for ELEMENT No TEXT-OUTPUT |
| No TEXT-OUTPUT |
|
|
|
|
| No TEXT-OUTPUT |
|
|
|
|
Converting from LMSCONV to LMS
All LMSCONV statements and operands are valid in LMS, provided that the full statement names or the guaranteed abbreviations are used. Thus, conversion from LMSCONV to LMS presents no problem to the user.