Hi Prashant;

  The POSA command is deprecated and should be replaced by the POS command. I suspect that during your migration and at the prompt dialogue, you checked the ANSI option and that is why the POS commands were altered. 

   Did you run the "Migration Assistant" in PB2017Rx on your PB 9 code before you migrated? This utility will point out any code that needs changing. If not, you should let PB2017Rx migrate your PB9 PowerScript to be Unicode compliant. PB9 was an ANSI based release. Since PB 10.0, PB is now Unicode. So the POSA use no longer makes sense to use unless, your parsing ANSI data.

Regards ... Chris

Hi Prashant,

it depends on your env. PB manual explains that "PosA replaces the functionality that Pos had in DBCS environments in PowerBuilder 9. In SBCS environments, Pos and PosA return the same results."

If you are not familiar with DBCS you can read here:

https://www.appeon.com/support/documents/appeon_online_help/pb2019/application_techniques/ch29s02.html

and use the GetEnvironment function to determine the character set used in the environment:

environment env
getenvironment(env)

choose case env.charset
case charsetdbcs!
// DBCS processing
...
case charsetunicode!
// Unicode processing
...
case charsetansi!
// ANSI processing
...
case else
// Other processing
...
end choose

Best,

.m