Conference microw::acmsxp

    Hi,
    
    I assume that this kit is the ACMSxp V3.0 kit for Digital Unix V4.0b?
    If this is the case the IVP is in error.  As of V4.0 of Digital Unix
    ACMSxp will no longer ship a version of libdce.so in the acmsxp kit.
    As this is a prerelease kit of ACMSxp on V4.0 the IVP hasn't been 
    corrected yet.  In fact I suspect their are several other problems
    with the IVP makefile besides the libdce problem.  On 4.0B of Digital
    Unix the linking of ACMSxp task and processing servers has changed.
    I suspect that change has not yet been propagated to the ivp makefile.
    I also don't know if the release notes have been updated to show how 
    to link on V4.0. 
    
    I'll send mail to the person who put the kit together asking him to 
    respond as well.
    
    Rich

Hello,

Thanks 

I wait for the response from the person who put the kit together.

Andre 

    
    Hi,
    
    Have you received the cover letter that explains the problems and
    suggested work arounds regarding this kit?  Basiclly the IVP and
    the examples included in this kit have not been updated to run on Unix 
    4.0.  There is also a pthreads bug that causes ACMSxp to hang.  We 
    hope to have a new kit that addresses these problems shortly.
    
    In the meantime here is an updated IVP makefile that should 
    fix the problems are you seeing with libdce:
    
# ****************************************************************************
# *
# * COPYRIGHT (C) DIGITAL EQUIPMENT CORPORATION 1993, 1994
# * ALL RIGHTS RESERVED.  UNPUBLISHED RIGHTS RESERVED UNDER THE
# * COPYRIGHT LAWS OF THE UNITED STATES.
# *
# * THIS SOFTWARE IS PROPRIETARY TO AND EMBODIES THE CONFIDENTIAL
# * TECHNOLOGY OF DIGITAL EQUIPMENT CORPORATION.  POSSESSION, USE, OR
# * COPYING OF THIS SOFTWARE AND MEDIA IS AUTHORIZED ONLY PURSUANT
# * TO A VALID WRITTEN LICENSE FROM DIGITAL EQUIPMENT CORPORATION
# * OR AN AUTHORIZED SUBLICENSOR.
# *
# * RESTRICTED RIGHTS: USE, DUPLICATION, OR DISCLOSURE BY THE
# * U.S. GOVERNMENT IS SUBJECT TO RESTRICTIONS AS SET FORTH IN
# * SUBPARAGRAPH (C) (1) (II) OF DFARS 252.227-7013, OR IN FAR
# * 52.227-19, OR IN FAR 52.227-14 ALT. III, AS APPLICABLE.
# *
# ****************************************************************************
#
# Description: Makefile for IVP
# History:
#
# Modification Date    Person   Edit Number  Description
#	   23/09/93    OD	T0.1	     Prepare for inclusion in kit.
#
#	   06/09/93    VB		     Add user written presentation

default: compile_stdl link

LFLAGS = -ldce -lpthreads -lpthread -lmach -lexc -lc \
	$(ACMS_SHLIB_DIR)/libsrtl.so \
	$(ACMS_SHLIB_DIR)/libtps.so
  
STDLFILES =		$(TWRK)/ivp_task_group_svr.o\
			$(TWRK)/ivp_task.o\
			$(TWRK)/workspaces.h

EXECS =			$(TWRK)/ivp_task_svr $(TWRK)/ivp


compile_stdl: $(STDLFILES)

$(TWRK)/ivp_task_group_svr.o: $(TSRC)/ivp_task_group.stdl
	stdl -g -o $(TWRK) -h $(TWRK) -c $(TSRC)/ivp_task_group.stdl

$(TWRK)/ivp_task.o: $(TSRC)/ivp_task.stdl
	stdl -g -o $(TWRK) -h $(TWRK) -t $(TSRC)/ivp_task.stdl

$(TWRK)/workspaces.h: $(TSRC)/workspaces.stdl
	stdl -g -o $(TWRK) -h $(TWRK) -c $(TSRC)/workspaces.stdl

link: $(EXECS)
$(TWRK)/ivp	:	$(TWRK)/ivp.o \
			$(TWRK)/ivp_task_svr
	cc -o $(TWRK)/ivp \
			$(TWRK)/ivp.o \
			$(TWRK)/ivp_task_group_cli.o \
			$(LFLAGS)

$(TWRK)/ivp_task_svr: $(TWRK)/ivp_task_group_svr.o \
			$(TWRK)/ivp_task.o
	cc -o $(TWRK)/ivp_task_svr \
                	$(TWRK)/ivp_task_group_svr.o \
                	$(TWRK)/ivp_task.o \
                	$(LFLAGS)
#
# Build the ivp menu client
#
$(TWRK)/ivp.o	:	$(TSRC)/ivp.c
		cc -threads -g -c -I$(STDL_SYSTEM_INCLUDE_PATH) -I$(ACMS_WORK_DIR) -o $(TWRK)/ivp.o \
		$(TSRC)/ivp.c
    

    Hi Andre,
    
    Is the customer the Kadaster?  Here are the caveats that were 
    shipped with the kit:
    
    Engineering will provide an early drop of ACMSxp V3.0 for
    Digital Unix V4.0 for Kadaster with the following caveats:
    
        - Usage: recommended for compile and builds only
    	- No regression or load testing has been completed 
    	- Engineering can not support ACMSxp V3.0 for Digital Unix V4.0 for
    	  production deployment at this time. Our testing and monitoring
    	  of problem reports against Digital Unix V4.0 indicates that
    	  Digital Unix V4.0 is not ready for production deployment.
    	- Microfocus COBOL with embedded SQL has not been tested
    	- Stop Server commands must be issues with /immediate switch
    	- Must set rpc_supported_protseq = ncacn_tcp_ip before starting 
    	  DCE
    
    	The following software is required for use with ACMSxp V3.0 for
        Digital Unix V4.0:
    	- Digital Unix V4.0b with patches from Feb 21, 1997
    	- DCE 2.0b with refresh credentials patch (not yet released, will
    	  be included with this ACMSxp kit)			
    
    	Engineering will provide an update kit in 2-4 weeks time. This kit
        will address some of the constraints listed above. It is likely
        that Digital UNIX V4.0 will continue to be unsuitable for production 
        deployment beyond this timeframe. In this case, an additional update of
        ACMSxp may be required.
    
    	Application (customer written clients and procedures) that utilize
        CMA or Draft 4 POSIX 1003.4a interfaces should be compiled using 
    	
    	%cc -o myprog myprog.c -threads
    
    	This will also cause pthread.h to include the proper dce/pthread_d4.h
        file for you with no source file modification.
    
    	When linking multithreaded images (task servers, processing
        servers and user written clients) use:
    
    	ld (...) -ldce lpthreads -lpthread -lmach -lexc -lc
    

    Please see note 279 for latest ACMSxp V3.0 for Digital Unix 4.0
    
    thanks

    Hello,
    
    sorry for the late response , but i was on a short vacation this week.
    The customer is  KADASTER
    
    greetings,
    
    Andre Hoornweg