Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	e-docs.beasys.com   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
WLE Doc Home   |   Messages   |   Catalog List   |   Previous   |   Next

CMDGW Messages 3400-3499

3417	ERROR: Can't read REMOTE SERVICES section of BDMCONFIG file (val)
	Description	While determining the size of shared memory, the DMADM administrative server could not access the DM_REMOTE_SERVICES (DM_IMPORT) section of the bdmconfig file.
	Action	Make sure that the bdmconfig file still exists.
	See Also	dmconfig(5)
3450	ERROR: GW_SEGSIZE must be a number, using calculated size
	Description	The environment variable GW_SEGSIZE must be specified with digit. If it contains none digit GWADM will ignore this environmental variable and, create shared memory using size calculated internally.
	Action	Shutdown the affected gateway group. Correct the GW_SEGSIZE environmental. And then reboot the gateway group.
	See Also	tmboot, ubbconfig
3451	ERROR: GW_SEGSIZE has too many digits, only 9 permitted
	Description	The environment variable GW_SEGSIZE specified too large, it will be ignored by GWADM.
	Action	Shutdown the affected gateway group. Correct the GW_SEGSIZE environmental. And then reboot the gateway group.
	See Also	tmboot, ubbconfig
3452	ERROR: GW_SEGSIZE must be greater than 0, using calculated size
	Description	The environment variable GW_SEGSIZE specified can not be 0 or negative. If it is 0 or of negative value GWADM will ignore this environmental variable, and create shared memory using size calculated internally.
	Action	Shutdown the affected gateway group. Correct the GW_SEGSIZE environmental. And then reboot the gateway group.
	See Also	tmboot, ubbconfig
3453	INFO: GW_SEGSIZE specified is smaller than calculated, use calculated size
	Description	The environment variable GW_SEGSIZE specified is smaller than needed to hold the configuration in shared memroy. The Gateway Administrative server GWADM will ignore this environmental variable, and create shared memory using size calculated internally.
	Action	Shutdown the affected gateway group. Correct the GW_SEGSIZE environmental. And then reboot the gateway group.
	See Also	tmboot, ubbconfig
3454	INFO: New segment size = val
	Description	The Gateway Administrative server GWADM will use the segment size specified in GW_SEGSIZE environmental variable to create shared memory.
	Action	Informational only, no action need to be taken.
3455	ERROR: Remote user mapping deleted successfully but can't delete the PRINAPPKEY entry val
	Description	The Domain configuration update operation successfully deleted the original local principal to remote principal mapping. But was not able to find the local principal's APPKEY.
	Action	This can happen if the user already deleted from the tpusr file, and this change already detected by GWADM and removed it.
3456	ERROR: Remote user mapping deleted successfully but can't find corresponding PRINAPPKEY entry to delete
	Description	The Domain configuration update operation successfully deleted the original local principal to remote principal mapping. But was not able to find the local principal's APPKEY.
	Action	This can happen if the user already been removed from the tpusr file, and this change already detected by GWADM and removed it. Or the user has not been added to tpusr file yet.
3457	ERROR: Can't setup principal-appkey mappings
	Description	The Domain configuration update operation successfully updated the local principal to remote principal mapping. But was not able to update the local principal's APPKEY information in shared memory.
	Action	This is caused by not able to expand shared memory. Shutdown the Gateway group and reboot it to grab more shared memory.
3458	ERROR: Remote user mapping deleted successfully but can't find corresponding PRINAPPKEY entry to delete
	Description	The /Domain configuration delete operation successfully removed the local principal to remote principal mapping, but it was not able to find the local principal's APPKEY.
	Action	This can happen if the user already been removed from the tpusr file, and this change already detected by GWADM and removed it. Or the user has not been added to tpusr file yet.
3459	ERROR: Remote user mapping deleted successfully but can't delete the PRINAPPKEY entry val
	Description	The /Domain configuration delete operation successfully removed the local principal to remote principal mapping, but it was not able to delete the local principal's APPKEY.
	Action	This can happen if the user already been removed from the tpusr file, and this change already detected by GWADM and removed it.