UMG_CONVERT_SPOOL: TemSe error when saving spool data

[] [] [] [] [] []

Symptom

The spool lists that were converted to Unicode by the report UMG_CONVERT_SPOOL are blank (length = 0 bytes).
In the log (created spool lists) of the report UMG_CONVERT_SPOOL, the system displays the following messages:
“Temse OPEN failed for SPOOL00000xxxxx”
“ERROR replacing Temse data!”

Other terms

Unicode, UMG_CONVERT_SPOOL
Reason and Prerequisites

When the system saved the list data that was converted to Unicode in the TemSe storage location, an error occurred in the TemSe function
RSTS_OPEN_WL.
Since the system deletes the old (non-Unicode) TemSe data from the spool request immediately before it calls this function, the converted spool lists are blank. The only spool requests that still exist are those created by UMG_CONVERT_SPOOL as back-ups of the original data.
In the “TemSe attributes” section in transaction SP01, the system displays code page 4102 or 4103 and a length of 0 bytes for spool requests for which the error occurred.
Solution

The report UMG_CONVERT_SPOOL is corrected. If a TemSe error occurs, the report now terminates the Unicode conversion of the old spool lists immediately and reports this accordingly in the log.
This problem is corrected in Release 7.20.
As of Release 6.20, you can import the relevant Support Package to correct this error.
Workaround:
The report ZUMG_SHOW_BAKUP is provided as an attachment to this note. You can create this report in the system to display a backup spool list.
Transaction SP01 cannot correctly display the spool requests that were created as backups because they contain non-Unicode list data.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment