ca.portal.admin

CALL IDMSCOMP BEFORE FINISH

Discussion created by ca.portal.admin on Nov 22, 2006
A 16.2 manual says to code CALL IDMSCOMP BEFORE FINISH and CALL IDMSDCOM
BEFORE FINISH in your Schema definitions for Areas containing compressed
records. The manual also says: This ensures that the work areas used by
the compression and decompression routines are freed when a rununit
terminates.



These CALL statements are sometimes missing in our Schemas. It would be
nice to know how large a penalty is being paid for this. Thanks.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
CALL IDMSCOMP BEFORE FINISH
"A 16.2 manual says to code CALL IDMSCOMP BEFORE FINISH and CALL IDMSDCOM
BEFORE FINISH in your Schema definitions for Areas containing compressed
records. The manual also says: This ensures that the work areas used by
the compression and decompression routines are freed when a rununit
terminates.



These CALL statements are sometimes missing in our Schemas. It would be
nice to know how large a penalty is being paid for this. Thanks.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Mulitasking & DC-COBOL Programs
"Chris,

For Uni-tasking, if a DC-COBOL program is sysgened with MPMODE SYSTEM or
ANY, the MPMODE will be ignored as it does not get process by the MT
codes. For that matter, uni-tasking will ignore the MPMODE of any
program (Assembler, Fortran, ADS Dialog). Hence you can leave your
DC-COBOL program MPMODE unchanged for your non multi-tasking system

Regards,
Paul Mak

Outcomes