RE: IBM Client access not working

Welly
All QUSRWRK, QSYSWRK, QSERVER are listed
all below ports are listening
Address Port Port Idle Time State
* * as-cent > 000:09:31 Listen
* * as-signon 000:09:41 Listen
* * as-svrmap 002:57:45 Listen
* * as-data > 002:57:45 Listen
done command
STRTCPSVR *ALL' and then 'STRHOSTSVR *ALL'
but still getting error CWBLM0031 failure a data conversion error was
returned by the host rc1=2 , rc2=21
In Blue part heading PC5250 License Error

-------- Original Message --------
Subject: RE: IBM Client access not working
From: "Welly@OCBCNISP" <[1]Welly@xxxxxxxxxxxx>
Date: Tue, July 25, 2017 8:59 pm
To: "'Midrange Systems Technical Discussion'"
<[2]midrange-l@xxxxxxxxxxxx>

Hi Ali,
1. For Subsystem search you can do
WRKSBS + Enter
- If QUSRWRK, QSYSWRK and QSERVER not listed there you should 'STRSBS
QUSRWRK' and 'STRSBS QSYSWRK' and 'STRSBS QSERVER'

2. For TCPServer
' WRKACTJOB SBS(QUSRWRK QSYSWRK QSERVER)'
Do Check if
- QZDASOINIT if listed (prestart job for TCPIP connection)
- QZDASRVSD if listed
- QZSOSMAPD if listed

And 'NETSTAT *CNN'
Please also check these daemons are listed and in listen mode
Remote Remote Local
Address Port Port Idle Time State
* * as-cent > 000:09:31 Listen
* * as-signon 000:09:41 Listen
* * as-svrmap 002:57:45 Listen
* * as-data > 002:57:45 Listen

If those above are not listed you should (this I usually do)
'STRTCPSVR *ALL' and then 'STRHOSTSVR *ALL'

Thanks for your help

Br,
Welly Soegiantoro
IT Services - Data Center

cug : 367090

-----Original Message-----
From: Welly@OCBCNISP [[3]mailto:Welly@xxxxxxxxxxxx]
Sent: Wednesday, July 26, 2017 7:56 AM
To: 'Midrange Systems Technical Discussion' <[4]midrange-l@xxxxxxxxxxxx>
Subject: RE: IBM Client access not working

HI Ali,
If we look @ CWBPING result, you should check
- Is QUSRWRK Subsystem started?
- Is QSYSWRK Subsystem started?
- Are TCP Servers Started?
- Are ClientAccess port allowed @ firewall
==> [5]http://www-01.ibm.com/support/docview.wss?uid=nas2II12227
(just allow what you need, no need to allow all)

Thanks for your help

Br,
Welly Soegiantoro
IT Services - Data Center

cug : 367090

-----Original Message-----
From: MIDRANGE-L [[6]mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of
[7]ali@xxxxxxxxxxxxxxx
Sent: Tuesday, July 25, 2017 9:45 PM
To: Midrange Systems Technical Discussion <[8]midrange-l@xxxxxxxxxxxx>
Subject: RE: IBM Client access not working

Guys for Client access for windows error i execute CWBPING command will
returns below results may be this will give good idea about problem. see
below message
IBM iSeries Access for Windows
Version 5 Release 3 Level 0
Connection Verification Program
(C) Copyright IBM Corporation and Others 1984, 2003. All rights
reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corp.
Licensed Materials - Property of IBM
To cancel the CWBPING request, press CTRL-C or CTRL-BREAK
I - Verifying connection to system 192.168.3.222...
I - Successfully connected to server application: Central Client
I - Successfully connected to server application: Network File
I - Successfully connected to server application: Network Print
I - Successfully connected to server application: Data Access
I - Successfully connected to server application: ODBC
I - Successfully connected to server application: Data Queues
I - Successfully connected to server application: Remote Command
I - Successfully connected to server application: Security
E - CWBCO1003 - Sockets error, function connect() returned 10061
E - CWBCO1049 - The iSeries server application (DDM) is not started
E - CWBCO1008 - Unable to connect to server application DDM, returned
10061
E - CWBCO1003 - Sockets error, function connect() returned 10061
E - CWBCO1049 - The iSeries server application (MAPI) is not started
E - CWBCO1008 - Unable to connect to server application MAPI, returned
10061
E - CWBCO1011 - Remote port could not be resolved
E - CWBCO1008 - Unable to connect to server application USF, returned
8407
E - CWBCO1003 - Sockets error, function connect() returned 10061
E - CWBCO1049 - The iSeries server application (Web Administration) is
not
started
E - CWBCO1008 - Unable to connect to server application Web
Administration, returned 10061
I - Successfully connected to server application: Telnet
E - CWBCO1003 - Sockets error, function connect() returned 10061
E - CWBCO1049 - The iSeries server application (Management Central) is
not
started
E - CWBCO1008 - Unable to connect to server application Management
Central, returned 10061
I - Successfully connected to server application: Service Tools
E - CWBCO1011 - Remote port could not be resolved
E - CWBCO1008 - Unable to connect to server application Operations
Console, returned 8407
E - CWBCO1011 - Remote port could not be resolved
E - CWBCO1008 - Unable to connect to server application Linux Console,
returned 8407
E - CWBCO1003 - Sockets error, function connect() returned 10061
E - CWBCO1049 - The iSeries server application (XDA) is not started
E - CWBCO1008 - Unable to connect to server application XDA, returned
10061
W - CWBCO1015 - Connection verified to system 192.168.3.222, but there
were warnings
Thanks

-------- Original Message --------
Subject: RE: IBM Client access not working
From: "Jim Hawkins" <[1][9]jhawkins@xxxxxxxxxxxx>
Date: Tue, July 25, 2017 6:25 am
To: <[2][10]midrange-l@xxxxxxxxxxxx>

I have been watching this thread and a thought came to me that I don't
think was brought up, what about damaged objects on the system. If the
power
down was not done properly, I know that in some cases damaged objects
can
result. Here is a link w/ a program to locate such objects.
[3][11]http://www.rpgpgm.com/2016/04/identifying-damaged-objects.html

> > Subject: IBM Client access not working
> >
> >
> > Hello guys
> > Please have a look at my problem below and advise need immediate
> help
> > System Restart from main panel due to backup job hanged in middle
> on
> > message waiting after restart the client access service for
windows
> not
> > working and its gives following Error CWBLM0031 - FAILURE, A DATA
> > CONVERSION ERROR WAS RETURNED BY HOST SERVER RC=1 2 RC2- =21 We
> > have a
> > valid client access license and its working before
> > Thanks in advance for any help.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: [4][12]MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [5][13]http://lists.midrange.com/mailman/listinfo/midrange-l
or email: [6][14]MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [7][15]http://archive.midrange.com/midrange-l.

Please contact [8][16]support@xxxxxxxxxxxx for any subscription related
questions.

Help support [9][17]midrange.com by shopping at [10][18]amazon.com with
our
affiliate link: [11][19]http://amzn.to/2dEadiD

References

Visible links
1. [20]mailto:jhawkins@xxxxxxxxxxxx
2. [21]mailto:midrange-l@xxxxxxxxxxxx
3. [22]http://www.rpgpgm.com/2016/04/identifying-damaged-objects.html
4. [23]mailto:MIDRANGE-L@xxxxxxxxxxxx
5. [24]http://lists.midrange.com/mailman/listinfo/midrange-l
6. [25]mailto:MIDRANGE-L-request@xxxxxxxxxxxx
7. [26]http://archive.midrange.com/midrange-l
8. [27]mailto:support@xxxxxxxxxxxx
9. [28]http://midrange.com/
10. [29]http://amazon.com/
11. [30]http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: [31]MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe,
or change list options,
visit: [32]http://lists.midrange.com/mailman/listinfo/midrange-l
or email: [33]MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a
moment to review the archives at
[34]http://archive.midrange.com/midrange-l.

Please contact [35]support@xxxxxxxxxxxx for any subscription related
questions.

Help support [36]midrange.com by shopping at [37]amazon.com with our
affiliate link:
[38]http://amzn.to/2dEadiD

--
Disclaimer :
Confidential information may be contained in this message.
If you are not the intended recipient, you are strictly prohibited and
may be unlawful to use, copy, store, distribute, disclose or
communicate any part of it to others and you are obliged to return
it immediately to sender or notify us and delete the e-mail and any
attachments from your system. Opinions, conclusions and other
information in this e-mail that do not relate to the official business
of any PT Bank OCBC NISP Tbk shall be understood as neither given
nor endorsed by it. No assumption of responsibility or liability
whatsoever is undertaken by PT Bank OCBC NISP Tbk in respect of
prohibited and unauthorised use by any other person.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: [39]MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [40]http://lists.midrange.com/mailman/listinfo/midrange-l
or email: [41]MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [42]http://archive.midrange.com/midrange-l.

Please contact [43]support@xxxxxxxxxxxx for any subscription related
questions.

Help support [44]midrange.com by shopping at [45]amazon.com with our
affiliate link: [46]http://amzn.to/2dEadiD

References

Visible links
1. mailto:Welly@xxxxxxxxxxxx
2. mailto:midrange-l@xxxxxxxxxxxx
3. mailto:Welly@xxxxxxxxxxxx
4. mailto:midrange-l@xxxxxxxxxxxx
5. http://www-01.ibm.com/support/docview.wss?uid=nas2II12227
6. mailto:midrange-l-bounces@xxxxxxxxxxxx
7. mailto:ali@xxxxxxxxxxxxxxx
8. mailto:midrange-l@xxxxxxxxxxxx
9. mailto:jhawkins@xxxxxxxxxxxx
10. mailto:midrange-l@xxxxxxxxxxxx
11. http://www.rpgpgm.com/2016/04/identifying-damaged-objects.html
12. mailto:MIDRANGE-L@xxxxxxxxxxxx
13. http://lists.midrange.com/mailman/listinfo/midrange-l
14. mailto:MIDRANGE-L-request@xxxxxxxxxxxx
15. http://archive.midrange.com/midrange-l
16. mailto:support@xxxxxxxxxxxx
17. http://midrange.com/
18. http://amazon.com/
19. http://amzn.to/2dEadiD
20. mailto:jhawkins@xxxxxxxxxxxx
21. mailto:midrange-l@xxxxxxxxxxxx
22. http://www.rpgpgm.com/2016/04/identifying-damaged-objects.html
23. mailto:MIDRANGE-L@xxxxxxxxxxxx
24. http://lists.midrange.com/mailman/listinfo/midrange-l
25. mailto:MIDRANGE-L-request@xxxxxxxxxxxx
26. http://archive.midrange.com/midrange-l
27. mailto:support@xxxxxxxxxxxx
28. http://midrange.com/
29. http://amazon.com/
30. http://amzn.to/2dEadiD
31. mailto:MIDRANGE-L@xxxxxxxxxxxx
32. http://lists.midrange.com/mailman/listinfo/midrange-l
33. mailto:MIDRANGE-L-request@xxxxxxxxxxxx
34. http://archive.midrange.com/midrange-l
35. mailto:support@xxxxxxxxxxxx
36. http://midrange.com/
37. http://amazon.com/
38. http://amzn.to/2dEadiD
39. mailto:MIDRANGE-L@xxxxxxxxxxxx
40. http://lists.midrange.com/mailman/listinfo/midrange-l
41. mailto:MIDRANGE-L-request@xxxxxxxxxxxx
42. http://archive.midrange.com/midrange-l
43. mailto:support@xxxxxxxxxxxx
44. http://midrange.com/
45. http://amazon.com/
46. http://amzn.to/2dEadiD