Show Contents List - Composer Version 6.1
The following activities were deprecated in LANSA Composer version 5.0 or earlier:
|
Original Activity Name: |
ARCHIVE_FILE |
|
Alternate Activity name: |
MOVE_FILE |
This activity was deprecated for the following reasons:
|
Original Activity Name: |
ARCHIVE_FILE2 |
|
Alternate Activity name: |
MOVE_FILE |
This activity was deprecated because it did not properly set the error result code when the file move fails.
|
Original Activity Name: |
CALL_FUNCTION |
|
Alternate Activity name: |
CALL_FUNCTION |
This activity was deprecated because the CALL_FUNCTION activity was enhanced with the ability to call functions in a different LANSA system and/or partition. In doing so, the number of supported exchange parameters was reduced to seven (7). The deprecated version of the activity preserves support for nine (9) exchange parameter values for existing Processing Sequences that may use them (but does not provide the enhanced capabilities of the new CALL_FUNCTION activity).
|
Original Activity Name: |
COPY_FILE |
|
Alternate Activity name: |
This activity was deprecated to ensure full upwards compatibility for existing solutions that use it when the COPY_FILE and related activities were enhanced to fully support pattern matching and destination file replace functionality. (There was a slight risk that solutions using directory and/or file names containing unusual characters might be adversely affected by the changes to the internal implementation that were necessary to support the new features.)
|
Original Activity Name: |
DELETE_FILE |
|
Alternate Activity name: |
This activity was deprecated to ensure full upwards compatibility for existing solutions that use it when the DELETE_FILE and related activities were enhanced to fully support pattern matching. (There was a slight risk that solutions using directory and/or file names containing unusual characters might be adversely affected by the changes to the internal implementation that were necessary to support the new features.)
|
Original Activity Name: |
DELETE_FILE |
|
Alternate Activity name: |
DELETE_FILE |
This activity was deprecated because it did not properly set the error result code when the file delete fails.
|
Original Activity Name: |
FTP_INBOUND |
|
Alternate Activity name: |
This activity was deprecated because of incorrect behaviour with respect to handling errors that occurred on the FTP GET operations. When this deprecated version was used, it assumed that, if it was able to LIST the file, therefore the GET would succeed. It therefore tolerated errors on the FTP GET and continued. This behaviour was INCORRECT and has been corrected in the revised FTP_INBOUND. However because existing implementations may have relied on this behaviour, this deprecated version maintains the previous behaviour.
|
Original Activity Name: |
FTP_INBOUND |
|
Alternate Activity name: |
FTP_INBOUND |
This activity was deprecated because of incorrect behaviour with respect to the use of the local target directory used by the activity. When this deprecated version was used with some FTP servers (especially Linux servers), then parts of the remote directory path may have been added to the target directory path. This behaviour was INCORRECT and has been corrected in the revised FTP_INBOUND. However because existing implementations may have relied on this behaviour, this deprecated version maintains the previous behaviour.
|
Original Activity Name: |
MOVE_FILE |
|
Alternate Activity name: |
This activity was deprecated to ensure full upwards compatibility for existing solutions that use it when the MOVE_FILE and related activities were enhanced to fully support pattern matching and destination file replace functionality. (There was a slight risk that solutions using directory and/or file names containing unusual characters might be adversely affected by the changes to the internal implementation that were necessary to support the new features.)
|
Original Activity Name: |
MSG_RECEIVE |
|
Alternate Activity name: |
MSG_RECEIVE |
This Activity was deprecated because it ends with an error status when no message is available to receive. The new version of the Activity ends with a normal (OK) status in this case, but a new output parameter contains a count of the messages received, allowing Processing Sequences that use it to better handle this case.
|
Original Activity Name: |
RENAME_FILE |
|
Alternate Activity name: |
This activity was deprecated to ensure full upwards compatibility for existing solutions that use it when related activities (COPY_FILE, DELETE_FILE and MOVE_FILE) were enhanced to fully support pattern matching. (There was a slight risk that solutions using directory and/or file names containing unusual characters might be adversely affected by the changes to the internal implementation that were necessary to support the new features.)
|
Original Activity Name: |
TUT_03_AT |
|
Alternate Activity name: |
NEXTNUMBER |
This activity was used in the tutorial exercise LIC004 provided with LANSA Composer version 2.0 and earlier. The tutorials supplied with LANSA Composer version 3.0 and later use the supplied NEXTNUMBER activity instead.