I am curious why you have this requirement. Maybe you have a different session in mind and are using tibom1411m000 simply as example.
My understanding is, unless the session is customized to recognize command line arguments, running it from the command line will just bring up the form so we can still continue and type in the required values and make the session run.
For example, I tried the following:
bin/bw.exe tibom1410m000 itemcode1 itemcode2
and the screen for tibom1410m000 came up as if I had run it from the menu. itemcode1 and itemcode2 were just ignored.
So, then I tried the following code:
item.f = argv$(1)
item.t = argv$(2)
and ran the session as before and the message commands showed me the values that I had passed to the command line. So, as far as customization goes, in the case of tibom1410m000, I would assign the first value to item.f, the next to item.t, (and so on) and then also customize to make the session pick ASCII as the device, force in some output file name, and make it proceed to choice.cont.process to get my output file.