Message Descriptions › VAM Messages › VAM0338

VAM0338

CALL TO MESSAGE SERVICE NOT MADE DUE TO REASON xxx

Reason:

This is an internal diagnostic message used by CA Technical Support. This message is conditionally issued when ever VAMVANT1, the CA Allocate message interface program, elects not to propagate a message onto another program product. The following are possible reasons:

1

ESTAE routine suppressed an abend.

2

Caller not using R13 for Dynamic Storage Area.

3

Caller not using R12 as primary base register, code 1.

4

Caller not using R12 as primary base register, code 2.

5

VKGPARMS or SYSPRT messages not propagated.

6

Caller neglected to use any calling parameters.

7

Calling parameter #1 missing, code 1.

8

Calling parameter #1 missing, code 2.

9

Calling parameter #2 missing, code 1.

10

Calling parameter #2 missing, code 2.

11

Calling parameter #3 missing, code 1.

12

Calling parameter #4 missing, code 1.

13

Calling parameter #2 missing, code 3.

14

PLSOPT78 value not (Y) or (N), code 1.

15

Cannot locate DTICVT control block.

16

Cannot locate PLUSCB control block, code 1.

17

Cannot locate PLUSCB control block, code 2.

18

PLSOPT78 value not (Y) or (N), code 2.

19

Calling parameter #2 missing, code 4.

20

Calling parameter #3 missing, code 2.

21

Logic error #1 found in message text.

22

Logic error #2 found in message text.

23

Calling parameter #2 missing, code 5.

24

Unable to determine message type.

25

Unable to access VANAPI01, code 1.

26

Unable to access VANAPI01, code 2.

27

Unable to access VANPUSER, code 1.

28

Unable to access VANPUSER, code 2.

29

Logic error related to TESTASRS job.

30

Logic error #1 related to CA Vantage PcGUI Message.

31

Unable to access VANPUSER, code 3.

32

Unable to access VANPUSER, code 4.

33

Unable to access VANPUSER, code 5.

34

NZ RC from VANPUSER, code 1.

35

NZ RC from VANPUSER, code 2.

36

Communication interface not initialized yet, code 1.

37

Communication interface not initialized yet, code 2.

38

Communication interface not initialized yet, code 3.

39

Communication interface not initialized yet, code 4.

40

Logic error #3 found in message text.

Action:

No action is necessary unless you are working directly with CA Technical Support. In that case, the complete JES Listing of the job or started task that received this message may be requested.