LANSA Partition not working

This Q&A forum allows users to post and respond to "How Do I Do ....." questions. Please do not use to report (suspected) errors - you must use your regional help desk for this. The information contained in this forum has not been validated by LANSA and, as such, LANSA cannot guarantee the accuracy of the information.
Post Reply
Balaji
Posts: 20
Joined: Tue Sep 19, 2017 6:05 pm

LANSA Partition not working

Post by Balaji »

Hi Al,

V13 VLF-WEB

WE have created multiple partitions(3 Partitions) under same lansa system, whereas while we try to access data it always points to the 1st partition.
Adding to this while we create partition system allowed us to create user for the 1st partition alone for the remaining two we were not able to create users pointing to their respective partitions.

Can you please help us address these two scenarios preferably at the earliest.

Thanks for your help in-advance.


Regards
Balaji
MarkD
Posts: 692
Joined: Wed Dec 02, 2015 9:56 am

Re: LANSA Partition not working

Post by MarkD »

What type of server is the LANSA system installed on?
MarkD
Posts: 692
Joined: Wed Dec 02, 2015 9:56 am

Re: LANSA Partition not working

Post by MarkD »

Assuming an IBM I server ……………..

When your server modules execute and access a database table it is almost always located by using the IBM i job’s library list.

Regardless of the partition being used, the thing to consider is what the server module’s library list is when you access a database table.
Balaji
Posts: 20
Joined: Tue Sep 19, 2017 6:05 pm

Re: LANSA Partition not working

Post by Balaji »

on IBM server.
Attachments
LANSA_IBM_SERVER.PNG
LANSA_IBM_SERVER.PNG (3.57 KiB) Viewed 7495 times
MarkD
Posts: 692
Joined: Wed Dec 02, 2015 9:56 am

Re: LANSA Partition not working

Post by MarkD »

Okay - so the library list of the job running your server module is the thing to look at.

There's 2 main considerations:
=> If you log on as different user, that will not change the job's library list like a 5250 session does. You need to do it yourself.
=> You need to do it on every single interaction with the server, because your requests may get routed into different IBM i jobs.
Post Reply