URGENT - Question on configuring Communication Server setting in AIX

Discussion:

(too old to reply)

Raymond Chan

2009-07-15 01:31:16 UTC

We would like to seek advice on starting the session for LU because we
found an internal error from the error log (sna.err).
We are able to connect to AS/400 up to the link station level.
But when we start to activate session for the LU ESBLU03 (our side -
RS6000) with DTDM251 (AS400), it shows the error of temporarily failed
to start the session.
We have checked the error log "sna.err" with the following error.

----------------------- 2009-07-14 09:46:48 CDT
-----------------------

LOG Message 4096 - 19, Subcode: 0 - 10

Log category: PROBLEM Cause Type: Internal

System: as2hkdapp06

ASSERT:

File name = ../../p/sappn/nsmutil.c

Line number = 298

Expression = (LOCAL.independent_lu) || (total_limit == 1)

------------------------------------------------------------------------------------

On the AS400 side, the LU name from DTDM251 to DTDM262 are created.

Thanks for your help.

Best Regards,

Raymond Chan

l***@attglobal.net

2009-07-15 09:48:24 UTC

Permalink

Post by Raymond Chan
We would like to seek advice on starting the session for LU because we
found an internal error from the error log (sna.err).
We are able to connect to AS/400 up to the link station level.
But when we start to activate session for the LU ESBLU03 (our side -
RS6000) with DTDM251 (AS400), it shows the error of temporarily failed
to start the session.
We have checked the error log "sna.err" with the following error.
----------------------- 2009-07-14 09:46:48 CDT
LOG Message 4096 - 19, Subcode: 0 - 10
Log category: PROBLEM Cause Type: Internal
System: as2hkdapp06
File name = ../../p/sappn/nsmutil.c
Line number = 298
Expression = (LOCAL.independent_lu) || (total_limit == 1)
-------------------------------------------------------------------
On the AS400 side, the LU name from DTDM251 to DTDM262 are created.
Thanks for your help.
Raymond Chan

You might need to post the sna_node.cfg and sna_domn.cfg
files from the AIX side and the AS/400's device description,
so we can see how the LUs are defined. They both need to
be independent LUs with parallel session support.

What mode name did you use when trying to start the session?
Can you try mode SNASVCMG first? How about a trying a pre-defined
mode like QPCSUPP? How is your user-mode defined in the as/400
('mode description')?

Do you know how to start and format a link station trace?
Does that show the CS/AIX box sending anything to the as/400
when the session start is attempted or does the failure happen
entirely within the aix box?

Paul Landay

Raymond Chan

2009-07-15 10:07:23 UTC

Permalink

I use Motif to config all the setting.

For sna_domn.cfg,

[define_domain_config_file]
major_version = 5
minor_version = 1
update_release = 1
revision_level = 17
comment = ""
updating = N

[set_global_log_type]
audit = YES
exception = YES
succinct_audits = NO
succinct_errors = NO

[define_cpic_side_info]
sym_dest_name = test cpi
description = ""
lu_alias = ""
partner_lu_name = ""
mode_name = " "
tp_name_type = APPLICATION_TP
tp_name =
<00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000>
conversation_security_type = NONE
security_user_id = ""
security_password = ""

[define_cpic_side_info]
sym_dest_name = JPING
description = ""
lu_alias = ""
partner_lu_name = ABC.AS400
mode_name = #INTER
tp_name_type = APPLICATION_TP
tp_name = APINGD
conversation_security_type = NONE
security_user_id = ""
security_password = ""

For JPing, after changing the lu_alias to our local cp name and
partner_lu_name = the partner CP name,
JPing shows a successful connection for them.

> We would like to seek advice on starting the session for LU because we
> found an internal error from the error log (sna.err).
> We are able to connect to AS/400 up to the link station level.
> But when we start to activate session for the LU ESBLU03 (our side -
> RS6000) with DTDM251 (AS400), it shows the error of temporarily failed
> to start the session.
> We have checked the error log "sna.err" with the following error.
>
> ----------------------- 2009-07-14 09:46:48 CDT
> LOG Message 4096 - 19, Subcode: 0 - 10
> Log category: PROBLEM Cause Type: Internal
> System: as2hkdapp06
> File name = ../../p/sappn/nsmutil.c
> Line number = 298
> Expression = (LOCAL.independent_lu) || (total_limit == 1)
> -------------------------------------------------------------------
>
> On the AS400 side, the LU name from DTDM251 to DTDM262 are created.
> Thanks for your help.
> Raymond Chan
You might need to post the sna_node.cfg and sna_domn.cfg
files from the AIX side and the AS/400's device description,
so we can see how the LUs are defined. They both need to
be independent LUs with parallel session support.
What mode name did you use when trying to start the session?
Can you try mode SNASVCMG first? How about a trying a pre-defined
mode like QPCSUPP? How is your user-mode defined in the as/400
('mode description')?
Do you know how to start and format a link station trace?
Does that show the CS/AIX box sending anything to the as/400
when the session start is attempted or does the failure happen
entirely within the aix box?
Paul Landay

Raymond Chan

2009-07-15 10:09:22 UTC

Permalink

Raymond Chan

2009-07-15 10:17:12 UTC

Permalink

Here is the config of sna_node.cfg

[define_node_config_file]
major_version = 5
minor_version = 1
update_release = 1
revision_level = 282

[define_node]
cp_alias = CPESB
description = ""
fqcp_name = BAAHKG.CPESB
node_type = NETWORK_NODE
mode_to_cos_map_supp = YES
mds_supported = YES
node_id = <07100000>
max_locates = 1500
dir_cache_size = 255
max_dir_entries = 0
locate_timeout = 60
reg_with_nn = YES
reg_with_cds = YES
mds_send_alert_q_size = 100
cos_cache_size = 24
tree_cache_size = 40
tree_cache_use_limit = 40
max_tdm_nodes = 0
max_tdm_tgs = 0
max_isr_sessions = 1000
isr_sessions_upper_threshold = 900
isr_sessions_lower_threshold = 800
isr_max_ru_size = 16384
isr_rcv_pac_window = 8
store_endpt_rscvs = NO
store_isr_rscvs = NO
store_dlur_rscvs = NO
cos_table_version = VERSION_0_COS_TABLES
send_term_self = NO
disable_branch_awareness = NO
cplu_syncpt_support = NO
cplu_attributes = NONE
dlur_support = YES
pu_conc_support = YES
nn_rar = 128
max_ls_exception_events = 0
max_compress_level = LZ10
ms_support = NORMAL
queue_nmvts = YES
clear_initial_topology = NO
ptf_flags = NONE

[define_ethernet_dlc]
dlc_name = ETHER0
description = ""
neg_ls_supp = YES
card_type = GDLC_ETHERNET
initially_active = NO
adapter_number = 0
max_saps = 16
ethernet_type = 802_3

[define_ethernet_dlc]
dlc_name = ETHER1
description = ""
neg_ls_supp = YES
card_type = GDLC_ETHERNET
initially_active = NO
adapter_number = 1
max_saps = 16
ethernet_type = 802_3

[define_ethernet_dlc]
dlc_name = ETHER2
description = ""
neg_ls_supp = YES
card_type = GDLC_ETHERNET
initially_active = NO
adapter_number = 2
max_saps = 16
ethernet_type = 802_3

[define_ethernet_port]
port_name = ESBP1
description = ""
dlc_name = ETHER1
port_type = PORT_SATF
port_number = 0
lsap_address = 0x04
initially_active = YES
implicit_hpr_support = YES
implicit_link_lvl_error = NO
implicit_uplink_to_en = NO
max_rcv_btu_size = 1492
tot_link_act_lim = 255
inb_link_act_lim = 0
out_link_act_lim = 0
ls_role = LS_NEG
implicit_dspu_services = NONE
implicit_dspu_template = ""
implicit_ls_limit = 0
act_xid_exchange_limit = 9
nonact_xid_exchange_limit = 5
ls_xmit_rcv_cap = LS_TWS
max_ifrm_rcvd = 7
target_pacing_count = 7
max_send_btu_size = 1492
mac_address = <664266426642>
implicit_cp_cp_sess_support = YES
implicit_limited_resource = NO
implicit_deact_timer = 30
effect_cap = 157286400
connect_cost = 0
byte_cost = 0
security = SEC_NONSECURE
prop_delay = PROP_DELAY_LAN
user_def_parm_1 = 128
user_def_parm_2 = 128
user_def_parm_3 = 128
local_name = ""
xid_timeout = 8
xid_retry_limit = 2
t1_timeout = 8
t1_retry_limit = 2
ack_time = 1
inact_time = 48
force_time = 120

[define_ethernet_ls]
ls_name = ESBL1
description = ""
port_name = ESBP1
adj_cp_name = <0000000000000000000000000000000000>
adj_cp_type = LEARN_NODE
dspu_services = NONE
dspu_name = <0000000000000000>
dlus_name = <0000000000000000000000000000000000>
bkup_dlus_name = <0000000000000000000000000000000000>
local_node_id = <00000000>
adj_node_id = <00000000>
conventional_lu_compression = NO
mac_address = <664200004266>
lsap_address = 0x04
max_send_btu_size = 1492
ls_attributes = SNA
cp_cp_sess_support = YES
hpr_supported = NO
hpr_link_lvl_error = NO
auto_act_supp = NO
tg_number = 0
limited_resource = NO
solicit_sscp_sessions = YES
pu_name = ESBL1
disable_remote_act = NO
default_nn_server = NO
link_deact_timer = 30
use_default_tg_chars = YES
effect_cap = 157286400
connect_cost = 0
byte_cost = 0
security = SEC_NONSECURE
prop_delay = PROP_DELAY_LAN
user_def_parm_1 = 128
user_def_parm_2 = 128
user_def_parm_3 = 128
target_pacing_count = 7
ls_role = USE_PORT_DEFAULTS
max_ifrm_rcvd = 0
dlus_retry_timeout = 0
dlus_retry_limit = 0
branch_link_type = NONE
adj_brnn_cp_support = ALLOWED
dddlu_offline_supported = NO
need_vrfy_fixup = NO
initially_active = NO
restart_on_normal_deact = NO
react_timer = 30
react_timer_retry = 65535
xid_timeout = 8
xid_retry_limit = 2
t1_timeout = 8
t1_retry_limit = 2
ack_time = 1
inact_time = 48
force_time = 120

[define_partner_lu]
plu_alias = dtdm251
description = ""
fqplu_name = BAAHKG.DTDM251
plu_un_name = dtdm251
parallel_sess_supp = YES
appcip_routing_preference = NATIVE
max_mc_ll_send_size = 0
conv_security_ver = NO

[define_partner_lu]
plu_alias = dtdm255
description = ""
fqplu_name = BAAHKG.DTDM255
plu_un_name = DTDM255
parallel_sess_supp = YES
appcip_routing_preference = NATIVE
max_mc_ll_send_size = 0
conv_security_ver = NO

[define_partner_lu]
plu_alias = dtdm256
description = ""
fqplu_name = BAAHKG.DTDM256
plu_un_name = DTDM256
parallel_sess_supp = YES
appcip_routing_preference = NATIVE
max_mc_ll_send_size = 0
conv_security_ver = NO

[define_partner_lu]
plu_alias = dtdm261
description = ""
fqplu_name = BAAHKG.DTDM261
plu_un_name = DTDM261
parallel_sess_supp = YES
appcip_routing_preference = NATIVE
max_mc_ll_send_size = 0
conv_security_ver = NO

[define_local_lu]
lu_alias = esblu03
list_name = ""
description = ""
lu_name = ESBLU03
lu_session_limit = 1
pu_name = ESBL1
nau_address = 4
default_pool = NO
syncpt_support = NO
lu_attributes = NONE
sscp_id = 0
disable = NO
sys_name = ""
timeout = 60
back_level = NO

[define_mode]
mode_name = MODEX
description = ""
max_neg_sess_lim = 32
plu_mode_session_limit = 8
min_conwin_src = 1
min_conloser_src = 0
auto_act = 0
receive_pacing_win = 4
max_receive_pacing_win = 0
default_ru_size = YES
max_ru_size_upp = 1024
max_ru_size_low = 0
cos_name = #CONNECT
compression = PROHIBITED
max_compress_level = NONE
max_decompress_level = NONE

[define_lu_pool]
pool_name = TEST
description = ""

Raymond Chan

2009-07-15 10:23:29 UTC

Permalink

For AS400 config,

it is an existing system and configured by client.
AS400 CP Name: BAAHKG.BAAHKGT
DEVICE from DTDM251 to DTDM262 are created for our local AIX
connection.

Raymond Chan

Raymond Chan

2009-07-15 10:38:35 UTC

Permalink

I have tried to use independent LU and dependent LU setting with
SNASVCMG mode in AIX side but both failed...
For the AS400 side, I need to confirm with my client on how to
configure them.

In the Motif GUI, I find that there is an option to generate trace
file. Can I use it to start and format the link station trace?

Raymond Chan

Raymond Chan

2009-07-15 10:49:55 UTC

Permalink

For the LU-LU connection, you said that I should use independent LU to
start the session. When I establish link station, it seems that there
is some data tranferred...
I am very frustruated in this moment. Actually we are now deciding to
use message broker for the project and establish conversation to AS400
through the Comm Server. But we stuck on the Comm Server config....

Raymond Chan

l***@attglobal.net

2009-07-15 12:42:20 UTC

Permalink

Post by Raymond Chan
But when I change the lu_alias to my dependent LU name and
and the actual partner lu name, JPing fail to connect...

Typically a Dependent LU is only used when the partner is a z/OS
host, i.e. VTAM. When CS/AIX talks to AS/400 you usually use
Independent LUs. You need to change the CS/AIX definition:

[define_local_lu]
lu_alias = esblu03
lu_name = ESBLU03
lu_session_limit = 1
pu_name = ESBL1
nau_address = 4

to be an Independent LU. Using the Motif Admin GUI it would
not be defined under the linkstation, but would be defined in
the middle third of the xsnaadmin panel. The resulting sna_node.cfg
entry would look more like this:

[define_local_lu]
lu_alias = esblu03
lu_name = ESBLU03
lu_session_limit = 0
pu_name =
nau_address = 0

Paul Landay

Raymond Chan

2009-07-15 15:35:17 UTC

Permalink

> But when I change the lu_alias to my dependent LU name and
> and the actual partner lu name, JPing fail to connect...
Typically a Dependent LU is only used when the partner is a z/OS
host, i.e. VTAM. When CS/AIX talks to AS/400 you usually use
[define_local_lu]
lu_alias = esblu03
lu_name = ESBLU03
lu_session_limit = 1
pu_name = ESBL1
nau_address = 4
to be an Independent LU. Using the Motif Admin GUI it would
not be defined under the linkstation, but would be defined in
the middle third of the xsnaadmin panel. The resulting sna_node.cfg
[define_local_lu]
lu_alias = esblu03
lu_name = ESBLU03
lu_session_limit = 0
pu_name =
nau_address = 0
Paul Landay

For Independent LU, it doesn't need to input the partner MAC address,
and also doesn't need to define self port and link station.
Physically, RS6000 (my CS/AIX) and AS400 are physically connected by
LAN.

Do you mean that when they are physically connected, they can detect
the opposite side LU?
I have also tried to set the LU as independent LU but there is
connection error...
You have just mentioned before in the previous post that AS400 LU
should also be independent, set to support parallel session and
SNASVCMG mode.
I guess the setting in AS400 doesn't like that so the connectoin fail.

Can I directly amend the sna_node.cfg file to update the change?
I guess it needs to stop sna > amend cfg file > start sna, is that
right?

Best Regards,
Raymond Chan

l***@attglobal.net

2009-07-15 13:14:06 UTC

Permalink

Post by Raymond Chan
In the Motif GUI, I find that there is an option to
generate trace file. Can I use it to start and format
the link station trace?

The 'Diagnostics' pop-up on the xsnaadmin main window
can be used to start and stop a link station trace,
but you need to use the 'snatrcfmt' command line command
to format the trace. Starting and stopping the trace from
the 'Diagnostics' pop-up will create the *.trc files in
the /etc/sna directory (for CS/AIX). The snatrcfmt command
will create the *.dmp files which are human-readable. See
the CS/AIX Diagnostics Guide for details on the snatrcfmt command.
The CS/AIX publications are online at:
http://www.ibm.com/software/network/commserver/aix/library/
You should stop the link trace before formatting it.

Paul Landay

Raymond Chan

2009-07-15 15:42:02 UTC

Permalink

> In the Motif GUI, I find that there is an option to
> generate trace file. Can I use it to start and format
> the link station trace?
The 'Diagnostics' pop-up on the xsnaadmin main window
can be used to start and stop a link station trace,
but you need to use the 'snatrcfmt' command line command
to format the trace. Starting and stopping the trace from
the 'Diagnostics' pop-up will create the *.trc files in
the /etc/sna directory (for CS/AIX). The snatrcfmt command
will create the *.dmp files which are human-readable. See
the CS/AIX Diagnostics Guide for details on the snatrcfmt command.
http://www.ibm.com/software/network/commserver/aix/library/
You should stop the link trace before formatting it.
Paul Landay

Do you have any idea on the error message in the first post?

File name = ../../p/sappn/nsmutil.c
Line number = 298
Expression = (LOCAL.independent_lu) || (total_limit == 1)

I wonder whether I have set anything wrong in my independent LU...
This error also pop-up when I start the dependent LU connection.

Best Regards,
Raymond Chan

l***@attglobal.net

2009-07-15 18:53:28 UTC

Permalink

Post by Raymond Chan
For Independent LU, it doesn't need to input the partner MAC address,
and also doesn't need to define self port and link station.
Physically, RS6000 (my CS/AIX) and AS400 are physically connected
by LAN.
Do you mean that when they are physically connected, they can
detect the opposite side LU?
I have also tried to set the LU as independent LU but there is
connection error...
You have just mentioned before in the previous post that AS400
LU should also be independent, set to support parallel session
and SNASVCMG mode.
I guess the setting in AS400 doesn't like that so the connectoin fail.
Can I directly amend the sna_node.cfg file to update the change?
I guess it needs to stop sna > amend cfg file > start sna,
is that right?
Best Regards,
Raymond Chan

An Independent LU is not directly associated with a link station.
In general it can use any link station to find its partner.
A Dependent LU is associated with one and only one link station.

In your case you only have one link station, so the Independent LU
will have to use that link to get to the as/400.

A Dependent LU can only have one session at a time,
it cannot do parallel sessions.
An Independent LU can have multiple sessions active
at a time, to one or more different partners.

My suggestion was NOT to change the link station definition
in any way, i.e. leave the DLC, port, ls alone; just to delete
the Dependent LU from that link station and define it as an
Independent LU.

The mode you are trying to use supports parallel sessions
and LU6.2 sessions between CS/AIX and AS/400 always (as far
as I recall) use Independent LUs, so I think you have to make
this change. If the CS/AIX LUs are defined in the AS/400
as Dependent then you have to change that side also; that
is why I suggested getting a copy of the as/400's
'Device Description'.

You can change the sna_node.cfg directly, by doing:
sna stop
vi /etc/sna/sna_node.cfg
sna start
If CS/AIX likes the changes the node will start.
If CS/AIX does not like the changes the 'sna start'
will fail and you will have to check the sna.err file
to see what it did not like.
I suggest making a back-up copy of sna_node.cfg before
doing any manual edits like this. Using snaadmin or
xsnaadmin is preferred because those commands check the
changes for validity long before the 'sna start'.

Paul Landay

l***@attglobal.net

2009-07-15 19:01:40 UTC

Permalink

Dear Paul,
Do you have any idea on the error message in the first post?

Post by Raymond Chan
File name = ../../p/sappn/nsmutil.c
Line number = 298
Expression = (LOCAL.independent_lu) || (total_limit == 1)

I wonder whether I have set anything wrong in my independent LU...
This error also pop-up when I start the dependent LU connection.
Best Regards,
Raymond Chan

An Independent LU allows more than one session.
A Dependent LU only allows one session at a time.
Therefore having an Independent LU with a lu_session_limit=1
does not make sense, or having a Dependent LU with a
lu_session_limit other than 1 does not make sense.

I believe that sna.err entry is saying you have a Dependent LU
which wants multiple sessions (probably SNASVCMG + MODEX).
That is why I think this needs to be an Independent LU:
[define_local_lu]
lu_alias = esblu03
lu_name = ESBLU03
lu_session_limit = 0
pu_name =
nau_address = 0
Note the lu_session_limit I suggested changing.

My guess is that this ESBLU03 LU is defined in the AS/400 as
Independent, but was defined in CS/AIX as Dependent (session_limit=1)
and when the as/400 tries to start the SNASVCMG session
CS/AIX sees the mismatch. That is a guess because we still
have not looked at the AS/400's 'Device Description' for ESBLU03
to make sure it is also Independent at that end.

Paul Landay

l***@attglobal.net

2009-07-15 20:41:54 UTC

Permalink

Until you get the ESBLU03 LU defined correctly on both the AS/400
and the CS/AIX sides, you could try starting a session using the
CP-LU on AIX to the target AS/400 LU DTDM251. The CP-LU is an
automatically defined LU which has the same name as the CS/AIX CP,
which is "CPESB" in your case. If you can start the MODEX session
from CPESB to DTDM251 then you know that you need to concentrate
getting the ESBLU03 definitions correct.

Paul Landay

Raymond Chan

2009-07-16 04:18:37 UTC

Permalink

Post by l***@attglobal.net

I have asked the client to send me the screen dump of the device
description and the mode description of MODEX.
The remote location for the device doesn't match with our LU setting
so we assume it is the reason for connection fail. But after our
client change the remote location to ESBLU03 (we define ESBLU03 link
with DTDM255), it still shows error..

I have also tried to use our CP-LU to connect their device using MODEX
but also fail....

When I try to use MODEX for ESBLU03 to connect with DTDM255, error
message box is pop-up with no error found in sna.err.
But when I use SNASVCMG to connect, it also has error in the sna.err
"UNBIND request received in response to a BIND request"

Is there any other setting going wrong so the connection still
fail...?

Best Regards,
Raymond Chan

Raymond Chan

2009-07-16 05:44:27 UTC

Permalink

One important finding from client side is that I discover the device
of DTDM251 to DTDm262 are active when the CP-CP connection is also
active. The devices seem to be auto-started before I establish the LU-
LU connection. Is it the reason when I start the LU-LU connection, on
the AS400 side, the device has already turned on so the LU-LU
connection fail?

Best Regards,
Raymond Chan

Raymond Chan

2009-07-16 10:58:00 UTC

Permalink

Today, we have tried to use aping in the command line to test the
connection on our own AIX and to AS400.
Result:
aping our cp - ok
aping our lu - ok
aping AS400 cp - ok (BAAHKG.BAAHKGT)
aping AS400 lu - all failed

And we have asked our client to use aping to test the connection in
their platform.
Result:
aping our cp - ok
aping our lu - ok
aping AS400 cp - failed
aping AS400 lu - all failed

It seems that none of us can access AS400 lu. Is there any security
setting blocked the access right to the LU on the AS400?

Actually, AS400 is using network node with connection to the other
parties. And we have change our AIX node to End Node after the aping
test.

In the sna.err log file, it shows that all the AS400 lu cannot be
found....

Best Regards,
Raymond Chan

l***@attglobal.net

2009-07-16 09:59:53 UTC

Permalink

Post by Raymond Chan
I have asked the client to send me the screen dump of the device
description and the mode description of MODEX.
The remote location for the device doesn't match with our
LU setting so
we assume it is the reason for connection fail. But after our client
change the remote location to ESBLU03 (we define ESBLU03 link with
DTDM255), it still shows error...(use independent LU to connect
1 + use independent LU to connect 2)
I have also tried to use our CP-LU to connect their device using MODEX
but also fail....
When I try to use MODEX for ESBLU03 to connect with DTDM255, error
message box is pop-up with no error found in sna.err.
But when I use SNASVCMG to connect, it also has error in the sna.err
"UNBIND request received in response to a BIND request"
Is there any other setting going wrong so the connection
still fail...?

The AS/400 definitions look ok to me, at least I don't see
anything obviously wrong. What does look wrong is that you
are only getting 1 CP-CP session. You should be getting 2
of them. Can you get a display of the CPESB description from
the AS/400 to compare to the CS/AIX [define_node] definition?
The sna.err shows you were getting sense code 08090039 for
that second CP-CP session. You can use this command to
display what that sense code means:
sna -getsense 08090039
Sorry that I did not see this yesterday. I think the 08090039
is because CS/AIX is defined as a NN and thinks the AS/400 is
an EN, but the AS/400 may not agree with that.

When you are getting a session setup failure pop-up but there
is no sna.err entry is when you need to do a link station trace.

Paul Landay

l***@attglobal.net

2009-07-16 11:36:16 UTC

Permalink

Dear Paul,
The session of CPSVCMG for CPESB - BAAHKG.BAAHKGT is 2 now....(strange
on aping 3.jpg)
Today, we have tried to use aping in the command line to test the
connection on our own AIX and to AS400.
aping our cp - ok
aping our lu - ok
aping AS400 cp - ok (BAAHKG.BAAHKGT)
aping AS400 lu - all failed
And we have asked our client to use aping to test the connection in
their platform.
aping our cp - ok
aping our lu - ok
aping AS400 cp - failed
aping AS400 lu - all failed
You can see in the attachment that there is session created for our
esblu03 with their baahkg.baahkgt (in strange on aping2.jpg)
It seems that none of us can access AS400 lu. Is there any security
setting blocked the access right to the LU on the AS400?
Actually, AS400 is using network node with connection to the other
parties. And we have change our AIX node to End Node after the aping

test.

In the attached sna.err log file, it shows that all the AS400 lu cannot
be found....
Best Regards,
Raymond Chan

Since you now have 2 cp-cp sessions the next thing I would do
is delete ALL the CS/AIX sna_node.cfg [define_directory_entry]
stanzas. Those stanzas pre-load the APPN databases, but with
working CP-CP sessions that is not needed as they are determined
automatically by APPN. If the [define_directory_entry] stanzas
are incorrect then you start with an APPN database which has
invalid info in it.

Paul Landay

l***@attglobal.net

2009-07-16 11:54:49 UTC

Permalink

Post by Raymond Chan
Today, we have tried to use aping in the command line to test the
connection on our own AIX and to AS400.
aping AS400 lu - all failed
And we have asked our client to use aping to test the connection in
their platform.
aping AS400 lu - all failed
It seems that none of us can access AS400 lu. Is there any security
setting blocked the access right to the LU on the AS400?

This is important. If the AS/400 cannot establish a session
with its own LU, then CS/AIX will not be able to do so.

There can be LU-LU security, as well as session security (two different
layers), but the sna.err does not show any security failures, just:
Locate search failed: LU not found.
Sense code = 0x08400007
Are you sure those are the LU names on the AS/400?
Those sna.err entries go on to say:
Action: Check that the target LU name is correct;
check that the system where this LU is defined is active

When aix or the as/400 tries to aping the as/400 LU are there
any messages in the as/400 "message log" (I think that is the right
name)? That is the as/400 equivalent of the sna.err and if
there are any messages there they may give you a clue as to why
the sessions to the as/400 LU fail.

Note that there if nothing in APPC or APPN that requires you use
an explicit LU name on the AS/400 side. You could use the AS/400's
CP LU as the target for all your sessions, even MODEX sessions.

Paul Landay

Raymond Chan

2009-07-16 14:38:51 UTC

Permalink

> Today, we have tried to use aping in the command line to test the
> connection on our own AIX and to AS400.
> aping AS400 lu - all failed
> And we have asked our client to use aping to test the connection in
> their platform.
> aping AS400 lu - all failed
> It seems that none of us can access AS400 lu. Is there any security
> setting blocked the access right to the LU on the AS400?

This is important. If the AS/400 cannot establish a session
with its own LU, then CS/AIX will not be able to do so.
There can be LU-LU security, as well as session security (two different
Locate search failed: LU not found.
Sense code = 0x08400007
Are you sure those are the LU names on the AS/400?
Action: Check that the target LU name is correct;
check that the system where this LU is defined is active
When aix or the as/400 tries to aping the as/400 LU are there
any messages in the as/400 "message log" (I think that is the right
name)? That is the as/400 equivalent of the sna.err and if
there are any messages there they may give you a clue as to why
the sessions to the as/400 LU fail.
Note that there if nothing in APPC or APPN that requires you use
an explicit LU name on the AS/400 side. You could use the AS/400's
CP LU as the target for all your sessions, even MODEX sessions.
Paul Landay

Dear Paul,

I will ask my client to check the security setting as well as the
message log.

In the AS400 GUI shown by my client, the devices (DTDM251 to DTDM26x)
are defined and active.
I will doble-check with the setting tmr...

If the LU connection problem is solved, I will implement the JPing
function into IBM websphere message broker in java compute node.
Whenever a message is passed to the java compute node, the message is
sent through CS/AIX to AS400 to the corresponding TP to receive the
message.
Do you know if it is possible to do so in this way...?

Best Regards,
Raymond Chan

l***@attglobal.net

2009-07-16 21:03:43 UTC

Permalink

Post by Raymond Chan
I will ask my client to check the security setting as well as the
message log.
In the AS400 GUI shown by my client, the devices (DTDM251 to DTDM26x)
are defined and active.
I will doble-check with the setting tmr...

Can the as/400 client confirm that DTDM251, etc are LUs
associated with that AS/400's CP name (BAAHKGT) and not
with some other CP on the other side of the AS/400?

When you tried to use DTDM251, etc are you sure you where
using the CS/AIX LU that the AS/400 was expecting (and not
the CS/AIX CP name)? See the next suggestion for how to
control which CS/AIX LU is being used.

Can I suggest that you go ahead and create
three cpic side info profiles, each with:
partner_lu = BAAHKGT
mode_name = MODEX
local_lu = ESBLU01, 02, 03
so you can test all three of the CS/AIX LUs to the AS/400 CP
while working on the AS/400 LUs.

Post by Raymond Chan
If the LU connection problem is solved, I will implement the JPing
function into IBM websphere message broker in java compute node.
Whenever a message is passed to the java compute node, the message is
sent through CS/AIX to AS400 to the corresponding TP to receive the
message. Do you know if it is possible to do so in this way...?

I think this is possible, but I am not a WebSphere person.
Keep in mind a couple of things:

1) You won't be using JPing on CS/AIX and APINGD on the AS/400
because those programs don't do anything with the data they
transfer. You can use those programs as models to write your
own CPI-C Transaction Programs.

2) JPing/aping do one 'short lived' instance of (to simplify):
cminit, cmalloc, cmsend, cmrecv, cmdeal
A WebSphere java applet / thread can be 'long lived' and
might be better designed to do:
cminit, cmalloc, infinite loop of
wait for new data to send
cmsend
cmrecv
if signaled by CS/AIX (return code not CM_OK) or by
Websphere, then do the cmdeal and end the applet.

Paul Landay

Raymond Chan

2009-07-17 04:37:56 UTC

Permalink

> I will ask my client to check the security setting as well as the
> message log.
>
> In the AS400 GUI shown by my client, the devices (DTDM251 to DTDM26x)
> are defined and active.
> I will doble-check with the setting tmr...
Can the as/400 client confirm that DTDM251, etc are LUs
associated with that AS/400's CP name (BAAHKGT) and not
with some other CP on the other side of the AS/400?
When you tried to use DTDM251, etc are you sure you where
using the CS/AIX LU that the AS/400 was expecting (and not
the CS/AIX CP name)? See the next suggestion for how to
control which CS/AIX LU is being used.
Can I suggest that you go ahead and create
partner_lu = BAAHKGT
mode_name = MODEX
local_lu = ESBLU01, 02, 03
so you can test all three of the CS/AIX LUs to the AS/400 CP
while working on the AS/400 LUs.
> If the LU connection problem is solved, I will implement the JPing
> function into IBM websphere message broker in java compute node.
> Whenever a message is passed to the java compute node, the message is
> sent through CS/AIX to AS400 to the corresponding TP to receive the
> message. Do you know if it is possible to do so in this way...?
I think this is possible, but I am not a WebSphere person.
1) You won't be using JPing on CS/AIX and APINGD on the AS/400
because those programs don't do anything with the data they
transfer. You can use those programs as models to write your
own CPI-C Transaction Programs.
cminit, cmalloc, cmsend, cmrecv, cmdeal
A WebSphere java applet / thread can be 'long lived' and
cminit, cmalloc, infinite loop of
wait for new data to send
cmsend
cmrecv
if signaled by CS/AIX (return code not CM_OK) or by
Websphere, then do the cmdeal and end the applet.
Paul Landay

Good News:

There is no configuration setting changed on the AIX side this morning
but I can now aping the AS400 lu BAAHKG.DTDM251 up to BAAHKG.DTDM262

Attached the screen dumps of successfully aping DTDM251 and DTDM262.

When I tried to aping DTDM301 up to DTDM332, the connection fail which
I think is a normal case as they are ready for EESBLU (another party)
only.

The LU-LU connection can also be established as shown in 'LU-LU
connection success.JPG'.

After that, I have followed your advice to delete ALL the CS/AIX
sna_node.cfg [define_directory_entry], and created cpic side info
profiles for ESBLU01 link to BAAHKG.DTDM251. And it works...

I think the client has changed the security setting without notice but
nevermind the problem is solved then it is ok....

You have suggested me to create 3 cpic side info profiles for ESBLU01
to 03, should I also create 3 different JPing.java as I found that the
symbolic destincation name in the java is hard-coded with "JPing "?
So I think that I need JPing01, JPinig02 and JPing03 with the symbolic
destincation name "JPing01 ", "JPing02 " and "JPing03 ".

Thank you for taking the time to discuss the Comm Server configuration
setting with me.
I really appreciate that you took so much time to help me to solve the
problem.

Best Regards,

Raymond Chan

l***@attglobal.net

2009-07-17 05:04:19 UTC

Permalink

I am glad you got it working.

You should not need 3 JPing.java, just 3 cpic side-info profiles.
According to the "CS/AIX CPI-C Programmer's Guide", the cpic-side
info profile name is a parameter that is passed to the JPing.class file.
For example:
# java JPing JPing01
The cpic side-info name does default to JPING.
Keep in mind that the cpic side-info may be case-sensitive,
so "JPING" is different from "Jping".

Paul

Post by Raymond Chan
There is no configuration setting changed on the AIX side this morning
but I can now aping the AS400 lu BAAHKG.DTDM251 up to BAAHKG.DTDM262
The LU-LU connection can also be established.
After that, I have followed your advice to delete ALL the CS/AIX
sna_node.cfg [define_directory_entry], and created cpic side info
profiles for ESBLU01 link to BAAHKG.DTDM251. And it works...
I think the client has changed the security setting without notice but
nevermind the problem is solved then it is ok....
You have suggested me to create 3 cpic side info profiles for ESBLU01
to 03, should I also create 3 different JPing.java as I found that the
symbolic destincation name in the java is hard-coded with "JPing "?
So I think that I need JPing01, JPinig02 and JPing03 with the symbolic
destincation name "JPing01 ", "JPing02 " and "JPing03 ".
Thank you for taking the time to discuss the Comm Server configuration
setting with me.